rust-lang / rust-lang/rust-analyzer
Allow flycheck to be configured to only check transitive dependents of the current crate
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
Forgot whether we already have an issue for this but currently we allow flycheck to check the whole workspace or only the crate itself, we shoukd have a third mode that checks the crate and its transitive dependents which ought to be faster than checking the whole workspace. The interesting question is whether this would make sense for cargo itself to have?
cc https://github.com/rust-lang/rust-analyzer/discussions/17379
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 flycheck's existing whole-workspace and current-crate modes, then read the linked rust-analyzer discussion and consider the Cargo implications mentioned in the issue. Done means a third configuration mode checks the current crate and its transitive dependents without checking unrelated workspace crates.
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