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)
Now that def returns the method name, it would be handy to have alias/alias_method return the name of the alias: class Foo private def foo() end protected alias_method :bar, :foo end Same goes for the attr_* methods: clas...rkh (Konstantin Haase)
eLobato (Daniel Lobato Garcia) wrote: > This error showed up in a Rails app, on my code I had two different files (ProxyAPI::Resource and ProxyAPI::BMC < Resource), and somehow there was a separated Resource class defined by a loaded ge...rkh (Konstantin Haase)