rust-lang / rust-lang/rust-analyzer
Adding a `use` should have higher priority than renaming to similar
Open
Nobody has claimed this yet.
A-diagnostics
E-has-instructions
E-medium
S-actionable
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
When there's some use of a symbol SomeTrait that's from some other module and there's a similar symbol in scope (like HasSomeTrait), the option to add a use for SomeTrait should appear in vscode's action list thing as the first item, above renaming to the similar symbol.
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, tests, or entry points. Start by locating the code-action ranking for unresolved symbols and the similar-symbol rename action, then compare their ordering when a use suggestion exists. Done means the use action appears first in the VS Code action list in that scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100