rust-lang / rust-lang/rust-analyzer
Improve completions when an `enum`-variant is expected
Open
Nobody has claimed this yet.
A-completion
C-feature
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
This case:
Should preferably suggest Self::NonTrivial(..) first/as one of the first suggestions.
This case:
Should suggest the variants first/should be included in the first suggestions.
In this case:
It's at least debatable whether the enum variants shouldn't be first in the list.
Maybe related Issues:
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 reproducing the three enum-completion examples in the issue and compare the current suggestion ordering. Trace rust-analyzer's completion ranking and enum-variant handling, then add focused regression coverage for the expected ordering and verify the related cases.
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
- 45/100