rust-lang / rust-lang/rust-analyzer

rust-analyzer can't work in files opened with absolute path

Open
#7,915 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-vscode C-bug E-unknown S-unactionable
Dominant language
Rust
Stars
16.9k
Forks
2.2k
Avg merge
1d 12h
Merged PRs (30d)
72

Description

image
can't work with name "problem_131.rs"
image
fine with name "problem131.rs"

rust-analyzer version v0.2.513

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

Start by reproducing the behavior in rust-analyzer v0.2.513 with a Rust file opened using an absolute path, comparing it with the working filename example from the report. Trace the file-opening and workspace handling entry points, then verify that both filenames work correctly in a current regression test or equivalent reproduction.

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
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.