Bug #20073: Method lookup incorrect with `--parser=prism`

• Status: Closed
• Assignee: -
• Target version: -
• Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN

[eightbitraptor (Matt V-H)]

The following code works with both CRuby's compiler and Prism when evaluated using RubyVM::InstructionSequence

~/git/ruby master ≡
❯ ./miniruby -d -e'p RubyVM::InstructionSequence.compile_prism("tap { }").eval'
main

~/git/ruby master ≡
❯ ./miniruby -d -e'p RubyVM::InstructionSequence.compile("tap { }").eval'
main

However when using the command line --parser=prism flag it results in a NoMethodError attempting to find tap, whereas CRuby's parser does not.

~/git/ruby master ≡
❯ ./miniruby -d -e'p tap { }'
main

~/git/ruby master ≡
❯ ./miniruby --parser=prism -d -e'p tap { }'
./miniruby: warning: The compiler based on the Prism parser is currently experimental and compatibility with the compiler based on parse.y is not yet complete. Please report any issues you find on the `ruby/prism` issue tracker.
Exception `NoMethodError' at <compiled> - undefined method `tap' for main
<compiled>:in `<compiled>': undefined method `tap' for main (NoMethodError)

This appears to be because the toplevel binding context is not being prepended to the linked list of instruction sequences when --parser=prism is passed.

[tenderlovemaking (Aaron Patterson)]

• Status changed from Open to Closed

Applied in changeset git|df0bfde2b29b7e8dac333b2a775ab8bff1283a5c.

---

We need to load builtins so that they work

Before this commit no methods defined in Ruby were being loaded. For
example class or tap methods would not exist.

[ruby-core:115793] [Bug #20073]