rust-lang / rust-lang/rustc-dev-guide
"name resolution"
Open
Nobody has claimed this yet.
A-resolve
C-enhancement
E-hard
T-compiler
- Dominant language
- HTML
- Stars
- 1.9k
- Forks
- 613
- Avg merge
- 17h 24m
- Merged PRs (30d)
- 39
Description
We should be talking about how the librustc_resolve crate works here. Some topics of interest:
- Handling scopes within the crate
- What is a rib? (#22)
- Where do ribs get added / removed, what happens if I need to introduce a binder? (#22)
- How does
pub useand stuff like that work - Globs and ambiguity
- How do names from external crates fit in?
Contributor guide
No contributing guide indexed for this repository
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 reading the existing material about the librustc_resolve crate and the completed rib topics. Document how pub use, globs, ambiguity, and names from external crates work, with the unchecked topics covered and the issue checklist updated when done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100