whitequark / whitequark/parser
1.8 char const + \u esc seq should be invalid syntax
Open
Nobody has claimed this yet.
bug
- Dominant language
- Yacc
- Stars
- 1.6k
- Forks
- 205
- PR merge metrics
- No merged PRs in 30d
Description
$ ruby-parse --18 -e "?\u267F"
(int 226)
$ ruby -e "?\u267F"
-e:1: syntax error, unexpected tINTEGER, expecting $end
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
Start by reproducing the discrepancy with ruby-parse --18 -e "?\u267F" and compare it with the Ruby command shown in the issue. Trace how the parser handles this character literal in Ruby 1.8 mode; done means the parser rejects it as invalid syntax like Ruby does.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100