rust-lang / rust-lang/rust-analyzer
Deduplicate diagnostics across `linkedProjects`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
In some cases, for compilation-related reasons (different target triples or compilation flags), it may be desirable to keep some parts of a single developer workspace/project not part of a single Cargo workspace (so that they do not share a target directory, or do not participate in workspace-wide build commands). If this is done, the option rust-analyzer.linkedProjects can be used to tell rust-analyzer about all of the Cargo workspaces within the project.
Currently, if a crate in one such workspace has a path dependency on a crate in another such workspace, the result will be that any warnings occurring in the latter are duplicated.
Feature request: Deduplicate warnings which are identical except for arising from distinct linkedProjects.
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 reproducing the duplicated warnings with multiple Cargo workspaces configured through rust-analyzer.linkedProjects, using a path dependency between them. Trace how diagnostics from the linked projects are collected and identify when warnings are identical except for their originating project. Done means each identical warning is reported only once while distinct diagnostics remain available.
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