Skip to content

Conversation

@ko1
Copy link
Contributor

@ko1 ko1 commented Jun 3, 2025

Ractor#value was newly introduced but it can be emulated with Ractor#take if Ractor.yield is not used.

https://bugs.ruby-lang.org/issues/21262

`Ractor#value` was newly introduced but it can be emulated with `Ractor#take` if `Ractor.yield` is not used.

https://bugs.ruby-lang.org/issues/21262
@eregon
Copy link
Member

eregon commented Jun 4, 2025

This feels wrong because I would never expect a test harness to define extra methods on core classes (except maybe assertions methods).
For instance it might lead people to believe Ractor#value is always available, and a gem might even rely on that, but the method doesn't exist on Ruby 3.4 and would break when someone actually uses it outside the test harness.
I think Ractor#take should be re-added in ruby/ruby (could be deprecated).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants