Actions
Feature #20460
openRipper `eval` option
Status:
Open
Assignee:
-
Target version:
-
Description
There are a couple of differences when producing syntax trees from the parser/ripper when compiling for eval. Namely, for the eval case it does not raise a syntax error for invalid jumps. It would be nice to be able to pass an eval: true/false
option to Ripper.sexp
/Ripper.sexp_raw
/Ripper.new
to tell it to parse as if it were an eval
.
Because of some new syntax errors, this had led to bugs like https://bugs.ruby-lang.org/issues/20186. If we provide such an option, it could also be useful for debugging purposes.
Updated by kddnewton (Kevin Newton) 6 months ago
- Tracker changed from Bug to Feature
- Backport deleted (
3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN)
Actions
Like0
Like0