Issue #8693 has been updated by rits (First Last).


rits (First Last) wrote:
> what is the reason for this?
> 
> why should yield and block.call behave differently?
> 
> why should lambdas sometimes not have lambda semantics?  When the code is written it has to assume lambda or proc semantics, it can't handle both, so why should the semantics vary?
> 
> PS email notification on bugs.ruby-lang.org is not working

@nobu - please explain
----------------------------------------
Bug #8693: lambda invoked by yield acts as a proc with respect to return
https://bugs.ruby-lang.org/issues/8693#change-40760

Author: rits (First Last)
Status: Rejected
Priority: Normal
Assignee: 
Category: 
Target version: 
ruby -v: ruby 2.0.0p247 (2013-06-27) [x64-mingw32]
Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN


irb(main):004:0> def m1; yield end; def m2; m1 &->{return 0}; 1 end; m2
=> 0



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