From: "luislavena (Luis Lavena)" Date: 2012-11-09T11:19:26+09:00 Subject: [ruby-core:49126] [ruby-trunk - Bug #7298] Behavior of Enumerator.new different between 1.9.3 and 2.0.0 Issue #7298 has been updated by luislavena (Luis Lavena). Category set to test Priority changed from Normal to Immediate Hello, I'm bumping the priority on this since it broke the build: http://www.rubyist.net/~akr/chkbuild/debian/ruby-trunk/log/20121109T003800Z.log.html.gz#test-all http://ci.rubyinstaller.org/job/ruby-trunk-x86-test-all/271/console Thank you ---------------------------------------- Bug #7298: Behavior of Enumerator.new different between 1.9.3 and 2.0.0 https://bugs.ruby-lang.org/issues/7298#change-32661 Author: ayumin (Ayumu AIZAWA) Status: Assigned Priority: Immediate Assignee: ayumin (Ayumu AIZAWA) Category: test 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/