From: nobu@... Date: 2017-01-09T03:52:29+00:00 Subject: [ruby-core:79020] [Ruby trunk Bug#12705] yielding args to a lambda uses block/proc rather than lambda/method semantics Issue #12705 has been updated by Nobuyoshi Nakada. What's the status? Is the current behavior on a lambda proc is intentional, and has the spec been changed since 2.2? And is the difference between a method proc and a lambda proc intentional, or not? If it is unintentional, splat for a method proc too? ---------------------------------------- Bug #12705: yielding args to a lambda uses block/proc rather than lambda/method semantics https://bugs.ruby-lang.org/issues/12705#change-62428 * Author: bug hit * Status: Assigned * Priority: Normal * Assignee: Koichi Sasada * Target version: * ruby -v: * Backport: 2.2: UNKNOWN, 2.3: REQUIRED, 2.4: REQUIRED ---------------------------------------- ```ruby def yield_test yield 1, 2 yield [1, 2] end def foo(a, b) p a, b end method_lambda = method(:foo).to_proc normal_lambda = ->a, b{p a, b} yield_test(&normal_lambda) yield_test(&method_lambda) ``` the yield of [1, 2] to the method_lambda produces an argument error as you would expect but the same yield to the normal_lamda does not, the single array arg is slpatted per block/proc semantics -- https://bugs.ruby-lang.org/ Unsubscribe: