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

resolve: Finish fixing #30159, a bug in import visibility #30866

Merged
merged 1 commit into from
Feb 1, 2016

Conversation

jseyfried
Copy link
Contributor

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,

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].

@jseyfried
Copy link
Contributor Author

r? @nrc
As discussed in #30324, this probably needs a crater run.

@nrc
Copy link
Member

nrc commented Jan 13, 2016

r+, so long as crater says nice things

@brson could you crater this please?

@bluss bluss added the S-waiting-on-crater Status: Waiting on a crater run to be completed. label Jan 13, 2016
@alexcrichton
Copy link
Member

Starting a crater run

@alexcrichton
Copy link
Member

Crater reports no regressions, but there are 544 unknown crates so it may not be super high fidelity (cc @brson)

@jseyfried
Copy link
Contributor Author

What is the status of this PR?
cc @nrc @brson

@bors
Copy link
Contributor

bors commented Jan 30, 2016

☔ The latest upstream changes (presumably #30843) made this pull request unmergeable. Please resolve the merge conflicts.

@jseyfried jseyfried force-pushed the fix_shadowed_use_visibility branch from 22ac9df to 7a69ee0 Compare January 31, 2016 02:25
@jseyfried
Copy link
Contributor Author

rebased

@nrc
Copy link
Member

nrc commented Feb 1, 2016

@bors: r+

@bors
Copy link
Contributor

bors commented Feb 1, 2016

📌 Commit 7a69ee0 has been approved by nrc

@nrc nrc removed the S-waiting-on-crater Status: Waiting on a crater run to be completed. label Feb 1, 2016
@nrc
Copy link
Member

nrc commented Feb 1, 2016

@jseyfried sorry, I lost track of this one

@jseyfried
Copy link
Contributor Author

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
Copy link
Contributor

bors commented Feb 1, 2016

⌛ Testing commit 7a69ee0 with merge 654f68d...

@bors bors merged commit 7a69ee0 into rust-lang:master Feb 1, 2016
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.

5 participants