Skip to content
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

rustc --print unstable-features #77937

Open
lnicola opened this issue Oct 14, 2020 · 1 comment
Open

rustc --print unstable-features #77937

lnicola opened this issue Oct 14, 2020 · 1 comment
Labels
A-stability Area: `#[stable]`, `#[unstable]` etc. C-feature-request Category: A feature request, i.e: not implemented / a PR. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Comments

@lnicola
Copy link
Member

lnicola commented Oct 14, 2020

It would be nice to have a --print unstable-features or -F help, because an IDE would then be able to offer auto-completions for tailored for the user's toolchain.

The best alternative today seems to be scraping the source code of https://doc.rust-lang.org/unstable-book/the-unstable-book.html.

@jonas-schievink jonas-schievink added A-stability Area: `#[stable]`, `#[unstable]` etc. C-feature-request Category: A feature request, i.e: not implemented / a PR. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Oct 14, 2020
@lnicola lnicola changed the title Request: rustc --print unstable-features rustc --print unstable-features Oct 14, 2020
@est31
Copy link
Member

est31 commented Oct 15, 2020

Code to collect all feature names in the compiler/std library would also be helpful for #77226 . I think for this param, the user should also specify whether there is a no_std/no_core context or whether std is included, because the list would be different each time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-stability Area: `#[stable]`, `#[unstable]` etc. C-feature-request Category: A feature request, i.e: not implemented / a PR. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

3 participants