rust-lang / rust-lang/rust-analyzer
Don't run initial flycheck when workspace loading failed
Open
Nobody has claimed this yet.
A-flycheck
C-bug
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
When the user changes their cargo toml causing us to reload the workspace with a failure we currently kick of cargo check which will immediately fail. We shouldn't attempt this!
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 by tracing the workspace reload path after a Cargo.toml change and the trigger for the initial flycheck run. Reproduce a failed workspace load, then verify that cargo check is not started in that case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100