rust-lang / rust-lang/rust-analyzer
Report compiler version mismatches more visibly
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
Sometimes while working on nightly, there's old compilation artifacts for cargo check that get found by cargo check, and it fails with some errors that they were made with a different compiler version. If this happens to r-a, they are not very visible, at least in editors that don't show the errors list prominently, leading users to wonder why there's no diagnostics they expect to be there in the current file.
I'd like if this particular error were injected into the top of the file like unlinked module errors are currently, as it would cause my ide to show there being errors. Either that or maybe do a pop up like project model cargo checks do.
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
Start with the troubleshooting guide and compare how unlinked module errors are surfaced with how project-model cargo checks report failures. Investigate the compiler-version mismatch from cargo check and determine where its diagnostic can be made visible in the editor. Done means users reliably see an error indicator or popup when this mismatch prevents expected diagnostics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100