Resolve some names during indexing
Open
Nobody has claimed this yet.
performance
- Dominant language
- Rust
- Stars
- 355
- Forks
- 24
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 17
Description
In cases like:
module Foo
module Bar; end
class Bar::Baz
end
end
Foo, Bar, and Baz can all be resolved during indexing, which will make global resolution faster by doing less work.
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
The issue names no files or tests. Start by locating the indexing and global-resolution entry points, then trace how the nested Foo, Bar, and Bar::Baz example is handled. Done means these names are resolved during indexing and the behavior is covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby, rust
- Domain
- compilers, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100