-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
[Rust 2018] pub use some_crate as some_name breaks glob imports #52141
Copy link
Copy link
Closed
Labels
A-edition-2018Area: The 2018 editionArea: The 2018 editionC-bugCategory: This is a bug.Category: This is a bug.F-rust_2018_preview`#![feature(rust_2018_preview)]``#![feature(rust_2018_preview)]`P-highHigh priorityHigh priorityT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.
Milestone
Metadata
Metadata
Assignees
Labels
A-edition-2018Area: The 2018 editionArea: The 2018 editionC-bugCategory: This is a bug.Category: This is a bug.F-rust_2018_preview`#![feature(rust_2018_preview)]``#![feature(rust_2018_preview)]`P-highHigh priorityHigh priorityT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Let's say lib.rs contains:
in order to make a crate available as a different name, using a glob import in the same crate (but other file) as such:
doesn't actually import anything into scope, while using explicit imports or
pub extern crate some_crate as some_name;instead works. This is possibly related to #52140