rust-lang / rust-lang/rust-analyzer

`unresolved import` for some `#[path = ".."]

Open
#3,898 10 comments 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-vfs S-actionable
Dominant language
Rust
Stars
16.9k
Forks
2.2k
Avg merge
1d 12h
Merged PRs (30d)
72

Description

unresolved import errors show up for:

  1. File paths whose extensions are not rs
  2. Absolute file paths
  3. Outside of the workspace (or simply workspace_root or somewhere?)

rust-analzyer

These files do exist.

$ tree -I target "$PWD"
/home/ryo/src/local/a
├── Cargo.lock
├── Cargo.toml
├── empty-file
├── empty-file.rs
└── src
    └── main.rs

1 directory, 7 files
$ touch ./src/main.rs && cargo clippy
    Checking a v0.1.0 (/home/ryo/src/local/a)
    Finished dev [unoptimized + debuginfo] target(s) in 0.47s
$ # OK

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the report from the listed project tree, including src/main.rs, empty-file, and empty-file.rs, using the noted stable Rust toolchain and rust-analyzer revision. Start by running cargo clippy and tracing the unresolved-import diagnostics for #[path] cases involving non-Rust extensions, absolute paths, and paths outside the workspace; done means existing paths no longer produce false errors.

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
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.