rust-lang / rust-lang/rust-analyzer
Emit diagnostic in opened files of workspaces whose sysroot failed to load
Open
Nobody has claimed this yet.
A-diagnostics
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
When the sysroot fails to load for a given workspace we ought to put a big error diagnostic at the top of the opened file if it belongs to such a workspace as this is always an error that needs to be fixed by the user
cc https://github.com/rust-lang/rust-analyzer/issues/17836#issuecomment-2277522510_
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 tracing workspace sysroot loading and the diagnostics path for opened files, then review the referenced rust-analyzer issue comment for context; done means an opened file in a workspace with a failed sysroot shows a prominent diagnostic while unaffected workspaces do not.
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
- 35/100