[#92063] [Ruby trunk Misc#15723] Reconsider numbered parameters — zverok.offline@...
SXNzdWUgIzE1NzIzIGhhcyBiZWVuIHVwZGF0ZWQgYnkgenZlcm9rIChWaWN0b3IgU2hlcGVsZXYp
3 messages
2019/03/31
[ruby-core:91759] [Ruby trunk Feature#15618] Implement Enumerator::Yielder#to_proc
From:
matz@...
Date:
2019-03-11 06:53:36 UTC
List:
ruby-core #91759
Issue #15618 has been updated by matz (Yukihiro Matsumoto).
Sounds reasonable.
Matz.
----------------------------------------
Feature #15618: Implement Enumerator::Yielder#to_proc
https://bugs.ruby-lang.org/issues/15618#change-77036
* Author: knu (Akinori MUSHA)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
----------------------------------------
When writing an Enumerator block, you often want to delegate iteration to another method like this:
```ruby
enum = Enumerator.new { |y|
Dir.glob("*.rb") { |file|
File.open(file) { |f| f.each_line { |line| y << line } }
}
}
```
I think this is such a common pattern, but the `{ |var| y << var }` part looks redundant compared to a normal iterator method being able to delegate to another method as simply as follows:
```
def each(&block)
@children.each(&block)
end
```
So, I propose adding #to_proc to Yielder so you can directly pass a yielder object to another method as a block argument.
```ruby
enum = Enumerator.new { |y|
Dir.glob("*.rb") { |file|
File.open(file) { |f| f.each_line(&y) }
}
}
```
Yielder is all about yielding, so I think it's pretty obvious what it means.
---Files--------------------------------
0001-Implement-Enumerator-Yielder-to_proc.patch (3.21 KB)
--
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>