-
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
Open tracking issues for all language features #28244
Comments
huonw
added
the
T-lang
Relevant to the language team, which will review and decide on the PR/issue.
label
Sep 4, 2015
huonw
added a commit
to huonw/rust
that referenced
this issue
Sep 8, 2015
This is similar to the libs version, which allow an `issue` field in the `#[unstable]` attribute. cc rust-lang#28244
bors
added a commit
that referenced
this issue
Sep 8, 2015
This is similar to the libs version, which allow an `issue` field in the `#[unstable]` attribute. cc #28244
triage: I-nominated. This has been very helpful for library features: promoting discussion, and allows people to track progress, so it'd be great to utilize properly for language ones too. |
triage: P-medium |
huonw
added a commit
to huonw/rust
that referenced
this issue
Oct 8, 2015
bors
added a commit
that referenced
this issue
Oct 9, 2015
aturon
added a commit
that referenced
this issue
Nov 10, 2015
This commit adds issue numbers to the vast majority of active feature gates. The few that are left without issues are rustc/runtime-internal features that are essentially private APIs. Closes #28244
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#26868 but for lang features.
The issues for each thing should be recorded in the corresponding place in
libsyntax/feature_gate.rs
, and when they've all been opened & recorded, the FIXME's relating to this issue in that file should be removed.The text was updated successfully, but these errors were encountered: