rust-lang / rust-lang/rust-analyzer
Highlighting exit points only works on `return` in VSCode
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
Companion issue to https://github.com/microsoft/vscode/issues/127007 to keep track of the issue on our side.
Basically exit point highlighting is supposed to work when the cursor is either on a return, ? or -> token but VSCode currently doesn't send the document highlight request unless the cursor is on a return or at the end of an identifier followed by a ?.
cc #9375
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
Begin with the linked VS Code issue #127007 and the rust-analyzer context around #9375; verify which side controls document highlight requests for return, ?, and ->. Done means exit-point highlighting is requested and works for all three cursor positions, with any rust-analyzer-side tracking updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100