This is supported on crate features
serde
and toml
only.Expand description
serde structures for parsing The Manifest Format
Why this over cargo_metadata?
cargo metadata
requires a valid workspace - missing crates etc. kill the whole commandmetadata
fields in cargo_metadata are just tables, I want them parameterized for easier usage- I also want spans and non-fatal errors for better error reporting and stuff
Modules
Structs
Cargo.toml
— The root of the parsed manifest, without context like “what was Cargo.toml’s path?”
[workspace]
— The workspace definition.