rust-lang / rust-lang/rust-analyzer
Inconsistent highlighting of string escapes
Open
Nobody has claimed this yet.
A-highlighting
C-bug
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
rust-analyzer version: 0.3.2555
rustc version: shouldn't matter
editor or extension: VS Code
code snippet to reproduce:
"\u{123}"; // highlights only `\u`
"\u{1234}"; // highlights the whole escape
b"\xff"; // highlights only `\x`
b"\x99"; // highlights only `\x`
b"\x00"; // highlights the whole escape
All of these strings are accepted by rustc.
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 in VS Code with rust-analyzer 0.3.2555 using the Rust snippets in the report, including the Unicode and byte-string escapes. Compare highlighting for valid escapes such as \u{123}, \u{1234}, \xff, and \x00; done means each valid escape is highlighted consistently while the snippets remain accepted by rustc.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100