rust-lang / rust-lang/rust-mode
Font-lock confused by apparent float suffix in non-decimal literal
Open
Nobody has claimed this yet.
- Dominant language
- Emacs Lisp
- Stars
- 1.3k
- Forks
- 198
- PR merge metrics
- No merged PRs in 30d
Description
The string 0xf64 is a hex literal (for the number 3940), but rust-mode highlights the f64 as a type suffix, making it appear to be a floating point number. This also happens when there are leading digits, such as in 0x1234f64.
Not a huge deal, but maybe something that you want to fix.
Contributor guide
No contributing guide indexed for this repository
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 highlighting problem with 0xf64 and 0x1234f64 in rust-mode, then trace the font-lock handling for numeric literals. Done means these hexadecimal literals are highlighted as numbers without treating the trailing f64 as a type suffix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- emacs, emacs-lisp, rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100