Steven Fackler

Both of those macros expand into values, not types.

Rustup seems to be what you're looking for: https://github.com/rust-lang/rustup#the-toolchain-file

> A toolchain that has the exact environment required to build that package. That's not what "toolchain" means to rustup. That sentence is just saying that the toolchain file specifies...

I'd like this in the context of platform dependent features that have dev-dependencies.

Yep, 1.41 is the current MSRV. The source of truth is what the CI build runs: https://github.com/sfackler/cargo-tree/blob/master/.circleci/config.yml#L5

Ah yeah, seems like it'd make sense to split out dependencies rooted at a `plugin = true` crate to `[plugin-dependencies]` or something like that.

That seems like a reasonable thing to do!

Have you taken a look at `cargo metadata`? That's the main interface for interacting programmatically with Cargo.

What do you mean by resolved features? I would kind of like to keep this project focused on user-facing output.

This seems reasonable. @alexcrichton any pointers on where to look in the cargo APIs? I need "download this pkgspec and well me where its directory is".