-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Make a better error message for using #[feature] on stable rust #26417
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
Conversation
r? @sfackler (rust_highfive has picked a reviewer for you, use r? to override) |
There are no tests for this error because with the current bootstrapping design it can't be emitted during the build. |
😢 Looks good to me! I'll be glad to get this improved. 🎊 |
It now says '#[feature] may not be used on the stable release channel'. I had to convert this error from a lint to a normal compiler error. I left the lint previously-used for this in place since removing it is a breaking change. It will just go unused until the end of time. Fixes rust-lang#24125
This LGTM but I'm gonna build a copy locally before I r+. If anyone else feels confident enough to do so in the meantime, feel free :) |
@bors: r+ |
📌 Commit f14a0e2 has been approved by |
It now says '#[feature] may not be used on the stable release channel'. I had to convert this error from a lint to a normal compiler error. I left the lint previously-used for this in place since removing it is a breaking change. It will just go unused until the end of time. Fixes #24125
It now says '#[feature] may not be used on the stable release channel'.
I had to convert this error from a lint to a normal compiler error.
I left the lint previously-used for this in place since removing it is
a breaking change. It will just go unused until the end of time.
Fixes #24125