rust-lang / rust-lang/rust-analyzer
Prefer to auto complete in scope word rather than import
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
I see a lot of issues about the scope of one import vs another. But I'm experiencing a lot of frustration when using the auto complete feature for in scope variables competing with auto import.
Example
This seems completely unexpected. I would assume local vars should always be prefered over importing a new module in terms of auto complete.
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 with rust-analyzer's autocomplete behavior for in-scope variables and competing auto-import suggestions, using the example in the issue as the reproduction case. Determine how completion choices are ranked, then verify that an in-scope variable is preferred over importing a new module while preserving expected auto-import behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100