From: "kddnewton (Kevin Newton) via ruby-core" Date: 2023-08-24T14:21:05+00:00 Subject: [ruby-core:114493] [Ruby master Misc#19772] API naming for YARP compiler Issue #19772 has been updated by kddnewton (Kevin Newton). I can also discuss multi-version support. Starting in December, we will release YARP version `3.3`. In this version, the C parser itself will be frozen so that developers can always have access to the same behavior as Ruby version `3.3`. The Ruby API, however, will still be able to be changed in order for developers to get new features (like I mentioned in the previous comment). At this point after the release, we'll begin developing on the `3.4` branch. If consumers of the gem want to parse code with `3.3`'s behavior, they will be able to use the old version of the gem. We will have the same maintenance cycle as CRuby does. ---------------------------------------- Misc #19772: API naming for YARP compiler https://bugs.ruby-lang.org/issues/19772#change-104278 * 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/ ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/