Bug #18193: Accessing global configuration from Ractors

• Status: Closed
• Assignee: -
• Target version: -
• ruby -v: ruby 3.0.2p107
• Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN

[kirs (Kir Shatrov)]

Consider a very common Ruby code with attr_accessor on a class:

class GlobalConfig
  class << self
    attr_accessor :option
  end
end

GlobalConfig.option = 123
GlobalConfig.freeze

puts GlobalConfig.frozen? # => true

r = Ractor.new do
  GlobalConfig.option
end

puts r.take

Right now, this fails can not access instance variables of classes/modules from non-main Ractors.

Is this considered a bug? If it is, I'd be happy to work on a fix.
To me, it seems like we should allow accessing frozen objects.

If this is expected behavior, then I'd like to open a conversation for how libraries and apps should expose things like global configuration for Ractors to consume.

[Eregon (Benoit Daloze)]

• Is duplicate of Feature #17592: Ractor should allowing reading shareable class instance variables added

[Eregon (Benoit Daloze)]

#17592 would let this work but it has not been implemented yet, cc @ko1 (Koichi Sasada)

[ko1 (Koichi Sasada)]

• Status changed from Open to Closed

https://github.com/ruby/ruby/pull/5006
merged.