Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This allows parsing the result of
cargo metadata
without having toimplement the json serialization in each caller, independently.
This is intended to be used by: rust-lang/rust#36032
This is the bare minimum required to implement the functionality required by rustc's bootstrap to determine the transitive dependency closure. Obviously, it would be nice if this were more fully featured. I initially tried copying the implementations from cargo with the intent of having cargo depend on this crate through a path dependency, just like it does with crates-io. However, this ended up being non-trivial, so I decided to limit the scope and start from scratch. Any thoughts on whether that would be a worthwhile approach (likely longer term)?