[#102652] [Ruby master Bug#17664] Behavior of sockets changed in Ruby 3.0 to non-blocking — ciconia@...
Issue #17664 has been reported by ciconia (Sharon Rosner).
23 messages
2021/02/28
[ruby-core:102537] [Ruby master Feature#17592] Ractor should allowing reading shareable class instance variables
From:
eregontp@...
Date:
2021-02-16 12:45:18 UTC
List:
ruby-core #102537
Issue #17592 has been updated by Eregon (Benoit Daloze).
ko1 (Koichi Sasada) wrote in #note-16:
> OK, you meant sharable or not, but not about class/module (class/module are typical cases, though).
Isn't it actually only about class/module though?
For a `Fixnum` or a `Ractor.make_shareable(Object.new)`, it's allowed to read @ivars. And it's a regular FrozenError to try to write an @ivar since they are frozen.
But for class/module, and I think only for those, it's currently not allowed to even read @ivars, even though class/module are considered shareable.
----------------------------------------
Feature #17592: Ractor should allowing reading shareable class instance variables
https://bugs.ruby-lang.org/issues/17592#change-90437
* 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: <mailto:[email protected]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>