rust-lang / rust-lang/rust-analyzer
Error messages disappear when `rustc-unicode` is enabled
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: 0.3.3033-standalone (f8996691e9 2026-08-30)
rustc version: rustc 1.100.0-nightly (f248f4038 2026-09-05)
editor or extension: VSCode, extension version 0.3.3033
relevant settings:
In config.toml
[unstable]
rustc-unicode = true
Doc: https://doc.rust-lang.org/cargo/reference/unstable.html#rustc-unicode
Tracking issue: https://github.com/rust-lang/rust/issues/148607
Steps to reproduce:
- Set the
rustc-unicode = truesetting inconfig.toml. - Create and open a simple Rust project in VSCode.
- Ensure that there are some errors or warnings in your main.rs.
- Run your file with the Run | Debug button near main.rs:
- Warnings disappear from code but still appear in the Problems tab:
Note the ╭▸ symbols in file path.
If you try to open this file VSCode will create it at the root of your drive:
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 issue with rustc-unicode enabled in config.toml and errors in main.rs, then inspect how rust-analyzer handles the compiler output containing the ╭▸ symbols. Confirm the fix by running the same VSCode scenario and verifying diagnostics remain attached to the source file rather than resolving at the drive root.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 67/100