Actions
Feature #20384
closedRubyVM::InstructionSequence.{new,compile} use --parser option
Status:
Closed
Assignee:
-
Target version:
-
Description
Right now we have RubyVM::InstructionSequence.compile
and RubyVM::InstructionSequence.compile_prism
. We introduced this API in order to properly test the integration, even when running with --parser=parse.y
.
I'm running into issues, however, when tests are comparing between eval
and RubyVM::InstructionSequence.new
. The latter always uses parse.y
, even if --parser=prism
is passed on the command line. I would like to change that so that RubyVM::InstructionSequence.{new,compile}
respects the --parser
option so that it's consistent.
Would this change be okay? It would only impact processes with --parser=prism
, so I don't imagine there's any kind of risk here.
Actions
Like0
Like0Like0