-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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 issue references to each #[unstable]
#26868
Comments
|
These are the libs team's official recommendations. Someone needs to write a script to autogenerate issues for each with these recommendations. Never stabilize
Ready for stabilization
Ready for deprecation
Need work
|
We don't want issues for any of these except the "Needs Work" category -- for the rest, we should just make PRs to stabilize or deprecate. Also, for the ones in Needs Work, each issue should give detail about the uncertainty in the design. Not sure that we should create the issues in bulk, rather than creating them hand-in-hand with these details (and grouping together as appropriate). Finally, we'll want some scheme for tagging these so that the subteam report script can pick them up for its dashboard. |
This commit turns `#[unstable]` attributes missing an `issue` annotation into a hard error. This will require the libs team to ensure that there's a tracking issue for all unstable features in the standard library. All existing unstable features have had issues created and they've all been updated. Yay! Closes #26868
#[unstable]
now supports theissue = "NNN"
field, that allows linking it to an issue here, e.g.#[unstable(feature = "foo", reason = "bar", issue = "1234")]
. We should use it more.The exact arrangement of which library features need issues/how those issues will be laid out is up in the air at the moment, so this issue isn't yet a call to action.
[TODO: make some sort of checklist]
cc @rust-lang/libs
The text was updated successfully, but these errors were encountered: