Expand description

See the stdlib documentation.

The difference between ::core::include_bytes! and this version of the macro is that, due to limitations of proc-macros in stable Rust, it is not possible to know whence a macro is called.

Thus, this macro requires it be called with a path that starts from the “root” of the package, i.e., a path that will be interpreted as if it started from: concat!(env!("CARGO_MANIFEST_DIR"), "/").