-
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
Tracking issue for Consistent no-prelude attribute (RFC 501) #20561
Comments
cc @Kimundi |
I think in theory primitive type definitions come from #![no_std]
use std::primitive_definition::* I know this change sounds trivial but current behavior is pretty ugly, see #22093 |
Triage: so. This RFC happened pre-1.0, yet never landed. And it seems |
Seems there has been a patch to implement this early this year, but it bitrottet: #32025 |
@rustbot label +S-tracking-design-concerns As noted by @petrochenkov here and @oli-obk here, its not clear if this change is still well-motivated. |
Team member @pnkfelix has proposed to close this. The next step is review by the rest of the tagged team members:
No concerns currently listed. Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for info about what commands tagged team members can give me. |
🔔 This is now entering its final comment period, as per the review above. 🔔 |
The final comment period, with a disposition to close, as per the review above, is now complete. As the automated representative of the governance process, I would like to thank the author for their work and everyone else who contributed. |
|
rust-lang/rfcs#501
The text was updated successfully, but these errors were encountered: