[ruby-core:95479] [Ruby master Feature#16261] Enumerable#each_tuple

Issue #16261 has been updated by Dan0042 (Daniel DeLorme).


@eregon Thank you very much for the enlightenment!

That means the code above could be rewritten like this. And at that point it's doubtful if `tuple` is even needed.

```ruby
class Enumerator
  def splat
    return to_enum(:splat) unless block_given?
    each_entry{ |item| yield(*item) }
  end
  def tuple
    return to_enum(:tuple) unless block_given?
    each_entry{ |item| yield(Array===item ? item : [item]) }
  end
end
```

----------------------------------------
Feature #16261: Enumerable#each_tuple
https://bugs.ruby-lang.org/issues/16261#change-82249

* Author: zverok (Victor Shepelev)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
----------------------------------------
New method proposal.

Prototype code:
```ruby
module Enumerable
  def each_tuple
    return to_enum(__method__) unless block_given?
    each { |item| yield(*item) } # unpacking possible array into several args
  end
end
```

Supposed documentation/explanation:

> For enumerable with Array items, passes all items in the block provided as a separate arguments. t could be useful if the provided block has lambda semantics, e.g. doesn't unpack arguments automatically. For example:

  ```ruby
files = ["README.md", "LICENSE.txt", "Contributing.md"]
content = [fetch_readme, fetch_license, fetch_contributing] # somehow make a content for the files

files.zip(content).each_tuple(&File.:write) # writes to each file its content
```

> When no block passed, returns enumerator of the tuples:

  ```ruby
[1, 2, 3].zip([4, 5, 6]).each_tuple.map(&:+) # => [5, 7, 9] 
```



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

Unsubscribe: <mailto:[e-mail]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>