Feature #22478: RbConfig::CONFIG could be Ractor-shareable by default?

• Status: Open
• Assignee: -
• Target version: -

[altruby (Alt Ruby)]

Hi

Is this intentional? The following code fails due to
Ractor::CONFIG not being Ractor-shareable.

##
# Ractor::IsolationError
require "rbconfig"
Ractor.new { 
  Process.wait Process.spawn(RbConfig.ruby, "-e", "p 123") 
}.value

This works fine but wouldn't be backwards compatible:

require "rbconfig"
Ractor.make_shareable(RbConfig::CONFIG)
Ractor.new { 
  Process.wait Process.spawn(RbConfig.ruby, "-e", "p 123") 
}.value

Would it be acceptable for RbConfig::CONFIG to
be deeply frozen, by default?

Thanks,