Feature #17286: `Ractor.new` should accept `move: true`

• Status: Open
• Assignee: -
• Target version: -

[marcandre (Marc-Andre Lafortune)]

Another surprise when writing my backport is that Ractor.new does not accept move: keyword argument.

Ractor.new(val, move: true) { |data| ... }
# equivalent to
Ractor.new { data = Ractor.receive; ... }.tap { |r| r.send(val, move: true) }

[ko1 (Koichi Sasada)]

I'm also thinking about the same feature, and the problem is, maybe we should choose move or copy on each parameters:

Ractor.new io,  # want to move
           str  # want to copy
do |io, str|
  io.puts str
end

and I have no good idea about it.

Ractor.new Ractor.move(io), str do...

is one idea (wrap with special object for passing argument), but not sure it is the best....

[marcandre (Marc-Andre Lafortune)]

I'd say let's start with a simple version and see what use-cases come up.

Seems already possible to mix and match anyways... Open the Ractor with one mode and yield the other parameters using the other mode.