Uh oh!
There was an error while loading. Please reload this page.
resolve: Finish fixing #30159, a bug in import visibility - #30866
Merged
Conversation
jseyfried
commented
Jan 13, 2016
ContributorAuthor
nrc
commented
Jan 13, 2016
Member
r+, so long as crater says nice things @brson could you crater this please? |
alexcrichton
commented
Jan 13, 2016
Member
Starting a crater run |
alexcrichton
commented
Jan 13, 2016
Member
Crater reports no regressions, but there are 544 unknown crates so it may not be super high fidelity (cc @brson) |
jseyfried
commented
Jan 30, 2016
ContributorAuthor
bors
commented
Jan 30, 2016
Collaborator
☔ The latest upstream changes (presumably #30843) made this pull request unmergeable. Please resolve the merge conflicts. |
… can make preceding imports public (fixesrust-lang#30159).
jseyfriedforce-pushed
the
fix_shadowed_use_visibility
branch
from
January 31, 2016 02:25
22ac9df to
7a69ee0Comparejseyfried
commented
Jan 31, 2016
ContributorAuthor
rebased |
nrc
commented
Feb 1, 2016
Member
@bors: r+ |
bors
commented
Feb 1, 2016
Collaborator
📌 Commit 7a69ee0 has been approved by |
nrc
commented
Feb 1, 2016
Member
@jseyfried sorry, I lost track of this one |
jseyfried
commented
Feb 1, 2016
ContributorAuthor
No problem |
bors added a commit
that referenced
this pull request
Feb 1, 2016
This reverts PR #30324, fixing bug #30159 in which a public a glob import makes public any preceding imports that share a name with an item in the module being glob imported from. For example, ```rust pub fn f() {} pub mod foo { fn f() {} } mod bar { use f; use f as g; pub use foo::*; // This makes the first import public but does not affect the second import. } ``` This is a [breaking-change].
bors
commented
Feb 1, 2016
Collaborator
bors
commented
Feb 1, 2016
Collaborator
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This reverts PR #30324, fixing bug #30159 in which a public a glob import makes public any preceding imports that share a name with an item in the module being glob imported from.
For example,
This is a [breaking-change].