-
Notifications
You must be signed in to change notification settings - Fork 13k
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: Make "empty import canaries" invisible from other crates #56117
Conversation
r? @oli-obk (rust_highfive has picked a reviewer for you, use r? to override) |
This is a fix for stable-to-beta regression, so I'm going to beta-nominate if it's not too late. r? @eddyb |
@bors r+ |
📌 Commit 1e4cf74 has been approved by |
@bors: p=1 |
⌛ Testing commit 1e4cf74 with merge 01deeb44d6df79efed934b4d7a9e002a3673e9d1... |
💔 Test failed - status-travis |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
Seems like Travis job just died in the middle of LLVM build. |
resolve: Make "empty import canaries" invisible from other crates Empty imports `use prefix::{};` are desugared into `use prefix::{self as _};` to make sure the prefix is checked for privacy/stability/etc. This caused issues in cross-crate scenarios because gensyms are lost in crate metadata (the `_` is a gensym). Fixes #55811
☀️ Test successful - status-appveyor, status-travis |
[beta] Rollup backports * #56163: [master] Backport 1.30.1 release notes * #56147: resolve: Fix some asserts in import validation * #56118: Update books for Rust 2018 * #56117: resolve: Make "empty import canaries" invisible from other crates * #56065: Replace the ICEing on const fn loops with an error * #56143: Issue 56128 segment id ice nightly * #56134: Fix clippy documentation links (first in #56156) r? @ghost
Empty imports
use prefix::{};
are desugared intouse prefix::{self as _};
to make sure the prefix is checked for privacy/stability/etc.This caused issues in cross-crate scenarios because gensyms are lost in crate metadata (the
_
is a gensym).Fixes #55811