Issue #15743 has been updated by Eregon (Benoit Daloze). waheedi (Waheed Barghouthi) wrote: > The pull request you just created does not really reflect what you are saying, `The RubyVM module only exists on MRI. +RubyVM+ is not defined in` I'm just trying to clarify as much as possible the documentation, until the rename is done. If the module was named `CRuby` (or MRI or YARV), there wouldn't even be a need for an explanation that it's MRI-specific and not defined on other Ruby implementations :) > I definitely can see the confusion caused by calling it RubyVM but there were no other implementations when it started, and it made total sense at the time, and I believe changing it would not really help more than 2% of the Ruby enthusiasts and they already know about it by now :) I think it would help all people knowing about it (including MRI committers) by making it clear that it's only for MRI-specific features and not, e.g., for portable experimental features (#15752). > Have a good day Thanks, you too. ---------------------------------------- Feature #15743: RubyVM should be renamed to CRuby https://bugs.ruby-lang.org/issues/15743#change-77508 * Author: Eregon (Benoit Daloze) * Status: Open * Priority: Normal * Assignee: * Target version: Next Major ---------------------------------------- My understanding is that `RubyVM` is supposed to only exist on MRI/CRuby, and not on any other Ruby implementation. In fact, almost all features under `RubyVM` are not realistically implementable on other major Ruby implementations (JRuby, TruffleRuby, Rubinius). Unfortunately, the name doesn't reflect that it is specific to CRuby, e.g., JRuby/TruffleRuby/Rubinius are also "Ruby VMs". And as a result it is not clear for many Ruby users that RubyVM is CRuby-specific. The documentation is also unclear: ``` The RubyVM module provides some access to Ruby internals. This module is for very limited purposes, such as debugging, prototyping, and research. Normal users must not use it. ``` So I propose to rename RubyVM to CRuby. That way, it is clear for everyone that this module is CRuby-specific. It's also consistent with the JRuby module, the TruffleRuby module and the Rubinius module. Proposed migration path: * Introduce CRuby as an alias of RubyVM on `trunk`, and deprecate the RubyVM constant on `trunk` (for 2.7). * Remove `RubyVM` in Ruby 3.0. What do you think? cc @ko1 @k0kubun @headius -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>