From: eregontp@... Date: 2021-02-15T16:49:55+00:00 Subject: [ruby-core:102507] [Ruby master Feature#17592] Ractor should allowing reading shareable class instance variables Issue #17592 has been updated by Eregon (Benoit Daloze). ko1 (Koichi Sasada) wrote in #note-14: > Sorry, I couldn't understand this point. > There is no special for class/module as a receiver objects (implementation is special, but no Ruby-level difference). > Do I miss something? There is a behavior difference, before Ractor `@foo` would always work and never raise. And `@foo =` would only raise if the receiver is frozen. Inside a Ractor, currently `@foo` works unless `self.is_a?(Module)`, same for `@foo =` (the inconsistency I mention: the same syntax has widely different semantics based on the receiver). If we accept this proposal, then at least `@foo` on a Module works if the value can be safely read (= the value is shareable). ---------------------------------------- Feature #17592: Ractor should allowing reading shareable class instance variables https://bugs.ruby-lang.org/issues/17592#change-90401 * Author: marcandre (Marc-Andre Lafortune) * Status: Open * Priority: Normal * Assignee: ko1 (Koichi Sasada) ---------------------------------------- It would be very helpful if Ractor was allowing reading class instance variables from non-main Ractor. Currently is raises an IsolationError: ```ruby module Foo singleton_class.attr_accessor :config Foo.config = {example: 42}.freeze end Ractor.new { p Foo.config } # => IsolationError ``` This limitation makes it challenging to have an efficient way to store general configs, i.e. global data that mutated a few times when resources get loaded but it immutable afterwards, and needs to be read all the time. Currently the only way to do this is to use a constant and use `remove_const` + `const_set` (which can not be made atomic easily). I think that allowing reading only may be the best solution to avoid any race condition, e.g. two different Ractors that call `@counter += 1`. The only 3 scenarios I see here are: 0) declare the constant hack the official way to store config-style data 1) allow reading of instance variables for shareable objects (as long as the data is shareable) 2) allow read-write I prefer 1) -- https://bugs.ruby-lang.org/ Unsubscribe: