From: "ayumin (Ayumu AIZAWA)" Date: 2012-11-08T11:43:16+09:00 Subject: [ruby-core:49077] [ruby-trunk - Bug #7298][Assigned] Behavior of Enumerator.new different between 1.9.3 and 2.0.0 Issue #7298 has been updated by ayumin (Ayumu AIZAWA). Status changed from Feedback to Assigned Hi Mark, The given block has no mean. It is just same as above example. I wanted to show that this issue is not closed yet by testcode. I agreed what you said. When Enumerator.new called with args and blok, the block is ignored and it should have been a warning. Thus, I will fix example. (after my daywork) Thanks. ---------------------------------------- Bug #7298: Behavior of Enumerator.new different between 1.9.3 and 2.0.0 https://bugs.ruby-lang.org/issues/7298#change-32606 Author: ayumin (Ayumu AIZAWA) Status: Assigned Priority: Normal Assignee: marcandre (Marc-Andre Lafortune) Category: Target version: 2.0.0 ruby -v: ruby 2.0.0dev (2012-11-07 trunk 37528) [x86_64-darwin12.2.0] Under 1.9.3, when Enumerator.new was called with arguments and block, it return Enumerator object. But under trunk, it makes TypeError. $ ruby -v -e "p Enumerator.new([1,2,3]){|y|y.yield 4}" ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-darwin11.4.2] # $ ./ruby -v -e "p Enumerator.new([1,2,3]){|y|y.yield 4}" ruby 2.0.0dev (2012-11-07 trunk 37528) [x86_64-darwin12.2.0] -e:1:in `initialize': can't convert Array into Integer (TypeError) from -e:1:in `new' from -e:1:in `
' -- http://bugs.ruby-lang.org/