rust-lang / rust-lang/rust-analyzer
Option to disable red-underlining large blocks of code
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
Rust analyzer tends to fill the whole function or file with red, like this:
This is annoying, I tend to disable the plugin for a moment when that happens.
It happens when I'm in the middle of writing a new function, or refactoring a function, and the error is "wrong return type". Sometimes I satisfy it by providing a return statement first, even mocked one, but it doesn't work if I want multiple branches with different returns.
Another use-case is when opening/closing brackets don't match, and red color makes it more difficult to find what's wrong.
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 file or test is named. Start by reproducing the reported wrong-return-type and unmatched-bracket cases in the Rust analyzer plugin, then trace how diagnostics become red underlining. Done should provide a user-controlled way to reduce or disable large-block underlining while preserving useful diagnostics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100