-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Conversation
r+, so long as crater says nice things @brson could you crater this please? |
Starting a crater run |
Crater reports no regressions, but there are 544 unknown crates so it may not be super high fidelity (cc @brson) |
☔ The latest upstream changes (presumably #30843) made this pull request unmergeable. Please resolve the merge conflicts. |
… can make preceding imports public (fixes rust-lang#30159).
22ac9df
to
7a69ee0
Compare
rebased |
@bors: r+ |
📌 Commit 7a69ee0 has been approved by |
@jseyfried sorry, I lost track of this one |
No problem |
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].
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].