From: ko1@...
Date: 2020-10-26T15:26:35+00:00
Subject: [ruby-core:100575] [Ruby master Feature#17286] `Ractor.new` should	accept `move: true`

Issue #17286 has been updated by ko1 (Koichi Sasada).


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

```ruby
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.

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

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

----------------------------------------
Feature #17286: `Ractor.new` should accept `move: true`
https://bugs.ruby-lang.org/issues/17286#change-88207

* Author: marcandre (Marc-Andre Lafortune)
* Status: Open
* Priority: Normal
----------------------------------------
Another surprise when writing my backport is that `Ractor.new` does not accept `move:` keyword argument.

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




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

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>