rust-lang / rust-lang/rust-analyzer
Complete item qualifiers
Open
Nobody has claimed this yet.
A-completion
C-feature
E-unknown
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
We should be able to complete item qualifiers properly, example:
const $0 fn() {}
Here we should offer keyword completions like unsafe. This is very tricky to get right for the majority of cases since const could parse as an item on its own, and different items want different qualifiers.
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
No files, tests, or entry points are named. Start by reproducing completion at the const $0 fn() {} position and determine how item qualifiers are currently handled. Done means offering valid keyword qualifiers such as unsafe across the relevant item contexts without treating partial items incorrectly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100