From: "Yugui (Yuki Sonoda)" <yugui / yugui.jp>
>
> Yusuke ENDOH wrote:
>> I'd like to confirm one thing; will the stardard libraries be also frozen?
> 
> The standard libraries will also be frozen.
> If you have changes of some libraries or features, let me know it by
> replying to this message by tomorrow and commit it as soon as possible.


Before it's too late, I wanted to plead for the possibility
of restoring the enumerator behavior David Black describes
below:


From: "David A. Black" <dblack / rubypal.com>
To: "ruby-talk ML" <ruby-talk / ruby-lang.org>
Sent: Friday, September 12, 2008 4:37 PM
Subject: Re: Advanced conditionals
> 
> On Sat, 13 Sep 2008, Bill Kelly wrote:
>>
>> From: "David A. Black" <dblack / rubypal.com>
>>> 
>>> [...] but you cannot, any longer, do this:
>>> 
>>> irb(main):007:0> a = [1,2,3,4]
>>> => [1, 2, 3, 4]
>>> irb(main):008:0> e = a.enum_for(:map, &lambda {|x| x * 10 })
>>> => #<Enumerable::Enumerator:0x3d7444>
>>> irb(main):009:0> e.next
>>> => 10
>>> 
>>> You'll get 1 now, rather than 10. I'm still very puzzled by the
>>> removal of this capability.
>>
>> Maybe worth asking on ruby-core?  Still 13 days till the
>> feature freeze...!
> 
> I did. Shugo did discuss it some, but I'm afraid I still didn't
> understand, or maybe I just wasn't convinced. I think it probably
> boils down to efficiency, though it seems to me to be an example of
> something so powerful and potentially useful that efficiency wouldn't
> (up to a point) be a deal-breaker.


It seems to me like one of those great features where ruby
pleasently surprises you by doing what you expected.

Matz, et al: Is there no possibility to retain this behavior?


Thanks for your consideration,

Bill