Project

General

Profile

Bug #13404

Hash#any? yields arguments to lambdas with proc semantics

Added by nelhage (Nelson Elhage) over 3 years ago. Updated almost 3 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
-
ruby -v:
ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-darwin16]
[ruby-core:80580]

Description

l = ->(a, b) { true }

# Raises; Uses Enumerable#all?
{1 => 2}.all?(&l)

# Does not raise; Uses specialized Hash#any?
{1 => 2}.any?(&l)

The Enumerable behavior was changed (correctly) in #12705, but the Hash#any? implementation (introduced in r46866) still allows the lax behavior.


Related issues

Is duplicate of Ruby master - Bug #13391: wrong number of arguments error for Hash#map when lambda givenClosedko1 (Koichi Sasada)Actions
#1

Updated by nobu (Nobuyoshi Nakada) about 3 years ago

  • Is duplicate of Bug #13391: wrong number of arguments error for Hash#map when lambda given added

Updated by hsbt (Hiroshi SHIBATA) almost 3 years ago

  • Status changed from Open to Rejected

We continues to discuss #13391

Also available in: Atom PDF