From: eregontp@... Date: 2021-03-13T12:50:29+00:00 Subject: [ruby-core:102846] [Ruby master Feature#17684] Remove `--disable-gems` from release version of Ruby Issue #17684 has been updated by Eregon (Benoit Daloze). I think `--disable-gems` is also useful to investigate issues, e.g. RubyGems used to override `Kernel#warn` (fixed in Ruby 3). It can significantly simplify investigating issues with `require`. I agree it's not very common to need it for debugging, but it turned up useful a couple times. If it's not available for releases then it becomes inconvenient to investigate such cases. Also the impact on startup time is still significant, so for very short scripts it can be noticeable (especially if calling out to subprocesses or running many small scripts). That's something that can potentially be improved in CRuby and/or RubyGems. For instance by loading RubyGems lazily (`autoload :Gem`, try loading `rubygems` the first time `require` fails), which TruffleRuby does. Finally, I guess for JITs it's quite useful to limit the amount of code loaded on startup, so having `--disable-gems` to investigate JIT issues seems useful. If it only works on development builds, then again it's inconvenient to investigate a bug report from a user using a release. ---------------------------------------- Feature #17684: Remove `--disable-gems` from release version of Ruby https://bugs.ruby-lang.org/issues/17684#change-90904 * Author: hsbt (Hiroshi SHIBATA) * Status: Open * Priority: Normal ---------------------------------------- In my understand, `--disable-gems` is only debugging feature for ruby-core team. But some users enabled its option in test environment for performance or etc. So, `--disable-gems` option is wrong usage for some users. * https://github.com/rubygems/bundler/issues/7487#issuecomment-569901549 * https://github.com/rubygems/rubygems/pull/4440#issue-587031184 We should remove it from package version of ruby. -- https://bugs.ruby-lang.org/ Unsubscribe: