rust-lang / rust-lang/rust-analyzer
False Positive "unresolved-import"
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
I am getting a false positive error in "unresolved-import" when I try to import a struct generated by a proc-macro in a separate crate.
Is there a way to override the error and quiet it, or maybe it could just be fixed. In the source code, it is clear the devs are aware of the issue
// This currently results in false positives in the following cases:
// - `cfg_if!`-generated code in libstd (we don't load the sysroot correctly)
// - `core::arch` (we don't handle `#[path = "../<path>"]` correctly)
// - proc macros and/or proc macro generated code

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
Use the reported separate-crate proc-macro import as the starting reproduction case, then inspect the unresolved-import implementation and the source comment listing proc-macro false positives. Done means the generated struct import no longer produces a false positive, or the issue documents a supported way to suppress it.
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