CRATE | CRATE is a real-time distributed CollaboRATive Editor

Redis doesn't define structured serialization formats. It mostly store strings and integers. So you have to choose or define your format for your struct.

A popular one is JSON, as you noticed, but if you just want to (de)serialize simple pairs of (id, description), it's not very readable nor convenient.

In such a case, you can define your own format, for example the id and the description with a dash in between:

Starting from version 0.5 of Rocket, you are not expected to use rocket_contrib, because this one was split into features which are either already in the core crate or moved to separate crates. The notes from this revision (see also issue 1659) provide a few more details:

This follows the completed graduation of stable contrib features into core, removing 'rocket_contrib' in its entirety in favor of two new crates. These crates are versioned independently of Rocket's core libraries, allowing upgrades to dependencies without consideration for versions in core libraries.

'rocket_dyn_templates' replaces the contrib 'templates' features. While largely a 1-to-1 copy, it makes the following changes:

• the 'tera_templates' feature is now 'tera'
• the 'handlebars_templates' feature is now 'handlebars'
• fails to compile if neither 'tera' nor 'handlebars' is enabled

'rocket_sync_db_pools' replaces the contrib 'database' features. It makes no changes to the replaced features except that the database attribute is properly documented at the crate root.

In short, you will need to migrate your code away from rocket_contrib. Better guidelines may become available once v0.5 is definitely released, but until then, you may look for the features once available in rocket_contrib in the core documentation and respective Cargo feature list.

This has been resolved. See above for the solution. It is marked with a header saying solution.

As per Lombok documentation (https://projectlombok.org/api/lombok/AllArgsConstructor.html):

An all-args constructor requires one argument for every field in the class.

Obviously you haven't provided id as a constructor argument.

In order to understand what's going on, I'll reformat the code a bit in order to make it more clear and explicit:

Your original code:

Your problem is not about lifetimes, you are using the wrong Json struct. You are using rocket::response::content::Json, this can be used to set the Content-Type of a response (see for example this). You want to use rocket::serde::json::Json:

After looking into the code and finding what looks a lot like the default entry point I'll put what I think is the confirmation of my guess as an answer: the global_allocator must be fully initialised before main, because the default entry point relies on it and allocates: https://github.com/rust-lang/rust/blob/master/library/std/src/rt.rs#L40-L45

1- Try changing

It seems like that one part of the use declarations created that problem. In the documentation (somewhere in some paragraph way to low that I looked at it) it says: " Streaming / Complete Some of nom's modules have streaming or complete submodules. They hold different variants of the same combinators.

A streaming parser assumes that we might not have all of the input data. This can happen with some network protocol or large file parsers, where the input buffer can be full and need to be resized or refilled.

A complete parser assumes that we already have all of the input data. This will be the common case with small files that can be read entirely to memory. "

Therefore, the solution to my problem is to swap use nom::character::complete::{char, space1}; instead of nom::character::streaming::{char, space1}; (3rd loc without counting empty lines). That worked for me :)