luke-gru (Luke Gruber) wrote in #note-2: > The tricky part in integrating the fiber scheduler with `Ractor::Port` `send/receive` is what to do when you want to wakeup (unblock) a fiber on another Ractor. Would it be possible to add s...rkh (Konstantin Haase)
Some objects cannot be moved (like unshareable lambdas). It would be great to have a method to check whether an object is movable, similar to `Ractor.shareable?`. Not 100% sure what it should return for shareable objects, but I wou...rkh (Konstantin Haase)
byroot (Jean Boussier) wrote in #note-6: > I understand the reasoning, however given the implementation of boxes, I fear implementing this proposal would reintroduce the need for many ractor locks, negating their usefulness. > ... This...rkh (Konstantin Haase)
ko1 (Koichi Sasada) wrote in #note-3: > > How will autoload work with this? > ... Right, but in the proposal you said: > A class/module records its creator Ractor as its owner. Only the owner may: > ... This does mean that modules ...rkh (Konstantin Haase)
How will autoload work with this? My understanding would be that autoload will simply not work from ractors, even on classes they own, except via `Ruby::Box`. Is that correct? Autoloads currently run on the main ractor, so ownershi...rkh (Konstantin Haase)
Interesting! I've been playing with workarounds in Ruby-land where I have up to one extra thread per Ractor, which executes `Ractor.select(coordinating_port, *ports)` with a backlog of waiting fibers per port, and then uses a `Conditi...rkh (Konstantin Haase)
Quickly upfront: This might be a duplicate of #20276, and let me know if the official solution is still to launch a thread for each port so it can block (or add some more complex thread orchestration). Anyway, I think `Ractor::Port#re...rkh (Konstantin Haase)
grosser (Michael Grosser) wrote: > Neither the release notes nor the wasm/README.md include any runnable examples. > ... I assume the final release will have an official .wasm file that ships with it. Note that the current approach ...rkh (Konstantin Haase)
This is failing on Travis CI and unfortunately preventing us from offering 2.2.0-preview2. See https://travis-ci.org/travis-ci/travis-rubies/jobs/42454368#L194 Konstantinrkh (Konstantin Haase)
rkh (Konstantin Haase)02:10 PM Ruby Bug #22211: Fiber::Scheduler stalls on Ractor::Port.receive