From: Yukihiro Matsumoto <matz@...>
Date: 2012-03-17T10:02:05+09:00
Subject: [ruby-core:43362] [ruby-trunk - Bug #6158] Enumerator::Lazy#take: should it be lazy?


Issue #6158 has been updated by Yukihiro Matsumoto.


use #first.  map! etc. do not conform other bang method naming convention.
----------------------------------------
Bug #6158: Enumerator::Lazy#take: should it be lazy?
https://bugs.ruby-lang.org/issues/6158#change-24668

Author: Benoit Daloze
Status: Assigned
Priority: Normal
Assignee: Shugo Maeda
Category: 
Target version: 
ruby -v: ruby 2.0.0dev (2012-03-15 trunk 35042) [x86_64-darwin10.8.0]


Hello,

I noticed #take is now defined on Enumerator::Lazy, and it has lazy behavior:

    (1..1000).lazy.select(&:even?).take 3 # => #<Enumerator::Lazy ...>

I would expect #take to not be lazy and always produce an Array, like the original Enumerable#take does.
I think many rubyists would expect that too.

Do you have a use case for a lazy #take ? I can't find one right now.

I've seen #6152, although I can't read it.
I think `lazy.take(5)` should be equal to `lazy.first(5)` and it reads better.


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