[ruby-core:56379] [ruby-trunk - Bug #8693] lambda invoked by yield acts as a proc with respect to return

Issue #8693 has been updated by mame (Yusuke Endoh).


rits (First Last) wrote:
> A "plain block" that "checks arguments" is an oxymoron.  Obviously such a thing should not exist.

I do not agree nor disagree with your opinion.


> Incidentally, here's another indication that under the current model, procs passed as blocks are not intended to be decomposed/unpacked into blocks (losing their proc shell in the process), but merely take the block slot as themselves (procs):

Imagine a natural Ruby implementation of proc:

  def proc(&blk)
    blk
  end

It does not use "yield".
It looks reasonable to me to return a lambda when lambda is given.


> The reason for consistency is avoiding surprise and bugs.

In general, compatibility beats consistency.
A better reason is often required to change a spec and/or behavior.
Matz sometimes does so according to his mood, though.

-- 
Yusuke Endoh <[e-mail]>
----------------------------------------
Bug #8693: lambda invoked by yield acts as a proc with respect to return
https://bugs.ruby-lang.org/issues/8693#change-40891

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/