rust-lang / rust-lang/rust-analyzer
Control flow should be deprioritized when not applicable
Open
Nobody has claimed this yet.
A-completion
C-enhancement
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
In other words, await should get a lower score in non-async context, continue in non-loop contexts and break in non breakable contexts. (We don't want to fully omit them since we could have assists/diagnostics in the future to fix up the contexts!)
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 in the issue. Start by locating rust-analyzer's control-flow completion ranking, then verify that await, continue, and break receive lower scores outside their applicable contexts while remaining available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100