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.

Sign up for GitHub

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

Jump to bottom

Tracking issue for no_std (RFC #1184) #27394

Closed
aturon opened this issue Jul 30, 2015 · 0 comments
Closed

Tracking issue for no_std (RFC #1184) #27394

aturon opened this issue Jul 30, 2015 · 0 comments
Labels
B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented.

Comments

@aturon
Copy link
Member

aturon commented Jul 30, 2015

rust-lang/rfcs#1184
@aturon aturon added the B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. label Jul 30, 2015
@alexcrichton alexcrichton mentioned this issue Jul 30, 2015
Closed
@aturon aturon mentioned this issue Jul 30, 2015
Merged
@alexcrichton alexcrichton mentioned this issue Jul 30, 2015
Merged
bors added a commit that referenced this issue Aug 5, 2015
@bors
Auto merge of #27393 - alexcrichton:no-std-changes, r=brson
dbe415a 
This commit is an implementation of [RFC 1184][rfc] which tweaks the behavior of
the `#![no_std]` attribute and adds a new `#![no_core]` attribute. The
`#![no_std]` attribute now injects `extern crate core` at the top of the crate
as well as the libcore prelude into all modules (in the same manner as the
standard library's prelude). The `#![no_core]` attribute disables both std and
core injection.

[rfc]: rust-lang/rfcs#1184

Closes #27394
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@aturon