[#71931] [Ruby trunk - Feature #11786] [Open] [PATCH] micro-optimize case dispatch even harder — normalperson@...

Issue #11786 has been reported by Eric Wong.

9 messages 2015/12/08

[ruby-core:72183] [Ruby trunk - Bug #11811] Chaining lazy enumerators causes duplicate ouput

From: shugo@...
Date: 2015-12-16 10:42:26 UTC
List: ruby-core #72183
Issue #11811 has been updated by Shugo Maeda.


Nobuyoshi Nakada wrote:
> Great, that's it.
> Please commit it.

Thanks for your confirmation.

I've committed it in r53152.
It's confusing that block->proc may not be a Proc, though....


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

* 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: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
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/

In This Thread

Prev Next