-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Command-line option to list supported feature-gate names #38768
Comments
Is this about language features, library features, or both? |
I'm not sure whether this is what you want, but do you know of the output of |
@rkruppe Both, for as long as std and rustc remain coupled. Anything supported in a |
@est31 I didn't. (I've seen that output before, just not the tool that generated it; thanks!) That would work, if available as a runtime option rather than a build-time command. |
Language features are listed in One wrinkle with the |
The option is only made available on nightly builds, for the obvious reason. While we're here, also prevent the unstable `target-spec-json` (tracking issue rust-lang#38338) from showing up in the --help on stable builds (although the way in which we accomplish this is slightly clumsy for lifetime reasons, as noted in the FIXME). We make REMOVED_FEATURES, ACCEPTED_FEATURES, &c. public for consistency, even though the functionality at issue only needs ACTIVE_FEATURES. The UI test will add a little bit of friction for future feature developers, but it's better than under-testing. Resolves rust-lang#38768.
#45223 was supposed to close this, but github didn’t for some reason. Closing! |
I'd like to have a command-line option to list all the supported feature-gate names in rustc. This would simplify the job of tools that want to detect the features supported by the installed version of rustc.
I don't know if introducing an option like this would require an RFC, or just a patch. Posting this as an issue to find that out before working on a patch.
The text was updated successfully, but these errors were encountered: