From: hanmac@...
Date: 2015-12-17T07:12:55+00:00
Subject: [ruby-core:72208] [Ruby trunk - Bug #11811] Chaining lazy enumerators causes duplicate ouput

Issue #11811 has been updated by Hans Mackowiak.


i don't know if thats the cause of it, but it seems that it did break this thing https://bugs.ruby-lang.org/issues/11830

----------------------------------------
Bug #11811: Chaining lazy enumerators causes duplicate ouput
https://bugs.ruby-lang.org/issues/11811#change-55618

* Author: Chris Beer
* Status: Closed
* Priority: Normal
* Assignee: Nobuyoshi Nakada
* ruby -v: ruby 2.3.0preview2 (2015-12-11 trunk 53028) [x86_64-darwin15]
* Backport: 2.0.0: DONTNEED, 2.1: DONTNEED, 2.2: DONTNEED
----------------------------------------
In Ruby 2.3.0-preview2, I'm seeing a change in behavior using lazy enumerators with select/reject and the & operator:

irb(main):037:0> %w(1 2 3).lazy.reject(&:empty?).each { |x| puts x }
1
1
2
2
3
3

Note that the output is doubled. However, if I don't use the & shorthand, the output is as expected:


irb(main):038:0> %w(1 2 3).lazy.reject { |x| x.empty? }.each { |x| puts x }
1
2
3
=> nil


And in Ruby 2.2.3, both variants produced the same result:

irb(main):001:0> %w(1 2 3).lazy.reject(&:empty?).each { |x| puts x }
1
2
3
=> nil


---Files--------------------------------
vm_caller_setup_arg_block.diff (1.03 KB)


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