Skip to content
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

Open
aturon opened this Issue Jan 5, 2015 · 4 comments

Comments

Projects
None yet
6 participants
@aturon
Copy link
Member

aturon commented Jan 5, 2015

@aturon

This comment has been minimized.

Copy link
Member Author

aturon commented Jan 5, 2015

@bombless

This comment has been minimized.

Copy link
Contributor

bombless commented Mar 5, 2015

I think in theory primitive type definitions come from std::*.
So if no_std or no_prelude is on there should not been primitive type definitions.
And I suggest we make alias of primitive types to a place like std::primitive_definition::*, so we write codes below to perform as no_std today:

#![no_std]
use std::primitive_definition::*

I know this change sounds trivial but current behavior is pretty ugly, see #22093
cc @mahkoh

@steveklabnik

This comment has been minimized.

Copy link
Member

steveklabnik commented Nov 30, 2016

Triage: so. This RFC happened pre-1.0, yet never landed. And it seems no_implicit_prelude does work on stable today. So, this would have to not be a re-naming, but a deprecation + new name?

@Kimundi

This comment has been minimized.

Copy link
Member

Kimundi commented Dec 3, 2016

Seems there has been a patch to implement this early this year, but it bitrottet: #32025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.