Skip to content

rustc: Future proof runtime injection #15987

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

Merged
merged 2 commits into from
Jul 26, 2014
Merged

rustc: Future proof runtime injection #15987

merged 2 commits into from
Jul 26, 2014

Conversation

brson
Copy link
Contributor

@brson brson commented Jul 25, 2014

Rename and gensym the runtime on import, so that users
can't refer to the native crate.

This is unlikely to break code, but users should import the "native" crate directly.

[breaking-change]

cc @alexcrichton

Rename and gensym the runtime on import, so that users
can't refer to the `native` crate.

This is unlikely to break code, but users should import the "native" crate directly.

[breaking-change]
@alexcrichton
Copy link
Member

Oh yes please! Could you add a test for this as well?

@brson
Copy link
Contributor Author

brson commented Jul 25, 2014

@alexcrichton Done.

// This is testing that users can't access the runtime crate.

// The rt has been called both 'native' and 'rt'
use native; //~ ERROR unresolved import
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FWIW, a use of a crate at the top level like this fails already: http://is.gd/MfQbdO (swapping the comments there allows it to compile.)

#13968

bors added a commit that referenced this pull request Jul 26, 2014
Rename and gensym the runtime on import, so that users
can't refer to the `native` crate.

This is unlikely to break code, but users should import the "native" crate directly.

[breaking-change]

cc @alexcrichton
@bors bors closed this Jul 26, 2014
@bors bors merged commit 6e03944 into rust-lang:master Jul 26, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants