Coloring character literals
Nobody has claimed this yet.
- Dominant language
- Racket
- Stars
- 8
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
DrRacket mis-colors some character literals, likely due to a mismatch between the documentation on character literals and the implementation of the reader. See racket/racket#3506 and racket/racket#3507 for examples of character literals that fall outside the spec given in the document, but are considered valid.
So #\U000000AA should be colored as a character literal, but is currently colored as a literal followed by an identifier AA. #\71 is colored as a character literal but should be red since it is not valid.
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
Start by comparing the documented character-literal rules with the two examples in the issue: #\U000000AA and #\71. Locate the syntax-color implementation and any related tests, then verify that the first is colored as one character literal and the second is marked invalid; no specific files or tests are named in the payload.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100