From: "altruby (Alt Ruby) via ruby-core" <ruby-core@...>
Date: 2026-10-27T19:06:15+00:00
Subject: [ruby-core:127254] [Ruby Feature#22478] RbConfig::CONFIG could be Ractor-shareable by default?

Issue #22478 has been reported by altruby (Alt Ruby).

----------------------------------------
Feature #22478: RbConfig::CONFIG could be Ractor-shareable by default?
https://bugs.ruby-lang.org/issues/22478

* Author: altruby (Alt Ruby)
* Status: Open
----------------------------------------
Hi

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

```ruby
##
# 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:

```ruby
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,




-- 
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/lists/ruby-core.ml.ruby-lang.org/