Module cargo::core::features

Support for nightly features in Cargo itself.

This file is the version of feature_gate.rs in upstream Rust for Cargo itself and is intended to be the avenue for which new features in Cargo are gated by default and then eventually stabilized. All known stable and unstable features are tracked in this file.

If you’re reading this then you’re likely interested in adding a feature to Cargo, and the good news is that it shouldn’t be too hard! First determine how the feature should be gated:

• New syntax in Cargo.toml should use cargo-features.
• New CLI options should use -Z unstable-options.
• New functionality that may not have an interface, or the interface has not yet been designed, or for more complex features that affect multiple parts of Cargo should use a new -Z flag.

See below for more details.

When adding new tests for your feature, usually the tests should go into a new module of the testsuite. See https://doc.crates.io/contrib/tests/writing.html for more information on writing tests. Particularly, check out the “Testing Nightly Features” section for testing unstable features.

After you have added your feature, be sure to update the unstable documentation at src/doc/src/reference/unstable.md to include a short description of how to use your new feature.

And hopefully that’s it!

New Cargo.toml syntax

The steps for adding new Cargo.toml syntax are:

1. Add the cargo-features unstable gate. Search below for “look here” to find the features! macro and add your feature to the list.

2. Update the Cargo.toml parsing code to handle your new feature.

3. Wherever you added the new parsing code, call features.require(Feature::my_feature_name())? if the new syntax is used. This will return an error if the user hasn’t listed the feature in cargo-features or this is not the nightly channel.

-Z unstable-options

-Z unstable-options is intended to force the user to opt-in to new CLI flags, options, and new subcommands.

The steps to add a new command-line option are:

1. Add the option to the CLI parsing code. In the help text, be sure to include (unstable) to note that this is an unstable option.
2. Where the CLI option is loaded, be sure to call CliUnstable::fail_if_stable_opt. This will return an error if -Z unstable options was not passed.

-Z options

The steps to add a new -Z option are:

1. Add the option to the CliUnstable struct below. Flags can take an optional value if you want.
2. Update the CliUnstable::add function to parse the flag.
3. Wherever the new functionality is implemented, call Config::cli_unstable to get an instance of CliUnstable and check if the option has been enabled on the CliUnstable instance. Nightly gating is already handled, so no need to worry about that.

Stabilization

For the stabilization process, see https://doc.crates.io/contrib/process/unstable.html#stabilization.

The steps for stabilizing are roughly:

1. Update the feature to be stable, based on the kind of feature:
2. cargo-features: Change the feature to stable in the features! macro below, and include the version and a URL for the documentation.
3. -Z unstable-options: Find the call to fail_if_stable_opt and remove it. Be sure to update the man pages if necessary.
4. -Z flag: Change the parsing code in CliUnstable::add to call stabilized_warn or stabilized_err and remove the field from CliUnstable. Remove the (unstable)` note in the clap help text if necessary.
5. Remove masquerade_as_nightly_cargo from any tests, and remove cargo-features from Cargo.toml test files if any.
6. Update the docs in unstable.md to move the section to the bottom and summarize it similar to the other entries. Update the rest of the documentation to add the new feature.

Structs

CliUnstable

A parsed representation of all unstable flags that Cargo accepts.

Feature

Features

Enums

Edition

The edition of the compiler (RFC 2052)

Constants

HIDDEN

SEE_CHANNELS

Functions

channel

Returns the current release channel (“stable”, “beta”, “nightly”, “dev”).