corona

Makes Serde serialize your data to the Rust source code.

Why?

This crate was inspired by the Stack Overflow question. In short, if you want to make some data in the human-readable format, such as JSON, to be deserialized at compile-time and build into the binary, as if it was written by hand, then this crate can possibly help you.

How to?

This crate is intended to be used from the build script. It will serialize anything you provide to it to any path you provide (or to the arbitrary io::Write implementation, if you want to). Then, you'll include! the generated file wherever you want to use it.

Is it really that simple?

Well... not. There are several limitations.

1. All the types used in the serialized struct must be in scope on the include site. Serde doesn't provide the qualified name (i.e. path) to the serializer, only the direct name. The probably easiest way is to use the serialized data as following:

let value = {
    use ::path::to::Type1;
    // ...and other types
    include!("path/to/file.rs")
}

or the similar construction using lazy_static. 2. As a consequence, all the types used by the serialized one must have distinct names (or they'll clash with each other). 3. Deserializer isn't implemented. This is intentional, since this crate isn't really intended for runtime usage.