rust-lang / rust-lang/reference
undocumented behavior: glob imports cannot shadow non-glob imports
Open
Nobody has claimed this yet.
A-use
Language Cleanup
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 607
- PR merge metrics
- PR metrics pending
Description
mod a {
pub fn b() { print!("1") }
}
mod c {
pub fn b() {
print!("2")
}
}
pub use c::b;
pub use a::*;
fn main() {
b(); // this prints "2"!
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Rust Reference section covering imports, glob imports, and name resolution, then use the example in the issue to verify the observed precedence. Document that the glob import does not shadow the explicit import, including the resulting call behavior; done means the example's behavior and rule are clearly explained.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100