Issue #19772 has been updated by hsbt (Hiroshi SHIBATA). This issue mixed many of topics. It's not for "YARP compiler". For Ruby core * Integration strategy of Ruby eval-ed parser. * How expose eval-ed parser for users. * And it's Naming For standalone gem * How bundle yarp as default gems or bundled gems. * Release cycle * Multi-version support * etc... @kddnewton @jemmai Can you categorize and summarize them to each new issue? ---------------------------------------- Misc #19772: API naming for YARP compiler https://bugs.ruby-lang.org/issues/19772#change-104409 * Author: jemmai (Jemma Issroff) * Status: Open * Priority: Normal ---------------------------------------- We are working on the YARP compiler, and have [the first PR ready](https://github.com/ruby/ruby/pull/8042) which introduces the YARP compile method. Our only outstanding question before merging it is about naming. How should we expose the public API for YARP's compile method? Potential suggestions: 1. YARP.compile 2. RubyVM::InstructionSequence.compile(yarp: true) 3. RubyVM::InstructionSequence.compile_yarp 4. Any of the above options, with a name other than yarp (please suggest an alternative) Regarding option 1, which would mirror `YARP.parse`, is the top level constant `YARP` acceptable? cc @matz @ko1 -- https://bugs.ruby-lang.org/