-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Add lint that all crates are #[unstable] #31122
Labels
A-testsuite
Area: The testsuite used to check the correctness of rustc
E-easy
Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
E-mentor
Call for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion.
Comments
👍 |
Since #31120 also was adding a single attribute everywhere, the lint might additionally look for other common crate attributes. |
I can mentor. |
Can I pick this up? I've been meaning to understand the business of lints. |
Manishearth
added a commit
to Manishearth/rust
that referenced
this issue
Feb 15, 2016
Manishearth
added a commit
to Manishearth/rust
that referenced
this issue
Feb 16, 2016
bors
added a commit
that referenced
this issue
Feb 16, 2016
bors
added a commit
that referenced
this issue
Feb 16, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-testsuite
Area: The testsuite used to check the correctness of rustc
E-easy
Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
E-mentor
Call for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion.
It's easy to forget to write it when adding new crates, as in #31120, and then release a crate as stable accidentally.
In tidy.py add a whitelist of crates that can be stable; in the loop, if the file name looks like 'src/*/lib.rs' it should have the attribute unless its on the whitelist.
The text was updated successfully, but these errors were encountered: