rust-lang / rust-lang/rust-analyzer
Unlinked-file diagnostic
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
rust-analyzer version: Output of rust-analyzer -V: rust-analyzer 1.84.0 (9fc6b43 2025-01-07). Or as available when using Zed 0.179.5
rustc version: rustc 1.84.0 (9fc6b4312 2025-01-07)
editor or extension: Zed 0.179.5
Have multiple packages in my workspace, when I bump a package abc's version 0.29.0 -> 0.30.0 in abc/Cargo.toml, while another package, say def, has in its own def/Cargo.toml:
[dependencies]
abc = { path = "../abc", version = "0.29.0" }
Opening any file from abc/src/, rust-analyzer says file is not included in any crates. What do I do? Note that only 0.29.0 is published, while 0.30.0 is not.
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
Reproduce the workspace described using abc/Cargo.toml, def/Cargo.toml, and a file under abc/src/. Start by inspecting rust-analyzer's workspace and package loading around the version mismatch, then trace the unlinked-file diagnostic; done means this case is handled correctly or its supported behavior is clearly established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100