Why does explicit return make a difference in a Proc?

Question

def foo   f = Proc.new { return "return from foo from inside proc" }   f.call # control leaves foo here   return "return from foo"  end  def bar   b = Proc.new { "return from bar from inside proc" }   b.call # control leaves bar here   return "return from bar"  end  puts foo # prints "return from foo from inside proc"  puts bar # prints "return from bar"  

I thought the return keyword was optional in Ruby and that you are always returning whether you request it or not. Given that, I find it surprising that foo and bar have different output determined by the fact that foo contains an explicit return in Proc f.

Does anyone know why this is the case?

Answer 1

Ruby has three constructs:

1. A block is not an object and is created by { ... } or do ... end.
2. A proc is a Proc object created by Proc.new or proc.
3. A lambda is a Proc created by lambda (or proc in Ruby 1.8).

Ruby has three keywords that return from something:

1. return terminates the method or lambda it is in.
2. next terminates the block, proc, or lambda it is in.
3. break terminates the method that yielded to the block or invoked the proc or lambda it is in.

In lambdas, return behaves like next, for whatever reason. next and break are named the way they are because they are most commonly used with methods like each, where terminating the block will cause the iteration to resume with the next element of the collection, and terminating each will cause you to break out of the loop.

---

If you use return inside the definition of foo, you will return from foo, even if it is inside a block or a proc. To return from a block, you can use the next keyword instead.

def foo   f = Proc.new { next "return from foo from inside proc" }   f.call # control leaves foo here   return "return from foo"  end puts foo # prints "return from foo"