Support nightly cargo features #4409
Comments
|
I've opened a PR for this at #4433 |
bors
added a commit
that referenced
this issue
Aug 25, 2017
Add infrastructure for nightly features and flags This PR starts adding infrastructure in Cargo for nightly features and nightly flags. The current design looks like: * There's a new `package.cargo-features` manifest key which accepts an array of strings. This array of strings is the list of enabled Cargo features for that crate. * A new suite of flags behind `-Z`, like the compiler, are accepted on the command line for all commands. * Features and unstable flags in Cargo are required to be used on Cargo's nightly channel, which is the same as Rust's nightly channel. * Features and unstable flags cannot be used on the stable/beta channels of Rust/Cargo. * Crates which enable features in their manifest are disallowed from being published to crates.io The motivation behind this support is unblock a number of efforts in Cargo by allowing them to safely get implemented behind a nightly feature gate. Once behind a feature gate they can iterate in-tree without having to worry about "insta stability" and we can also get valuable usage feedback about upstream users. Closes #4409
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We've long had a desire for features in Cargo that stay on the nightly channel or otherwise require opt-in. We should have support for this in Cargo.
The text was updated successfully, but these errors were encountered: