/lambda-vs-proc-vs-blocks/ Red Panthers - Experts in Ruby on Rails, System Design and Vue.js Sat, 17 Sep 2016 05:56:00 +0000 hourly 1 https://wordpress.org/?v=5.2.7 /lambda-vs-proc-vs-blocks/#comment-15 Sat, 17 Sep 2016 05:56:00 +0000 https://redpanthers.co/?p=467#comment-15 I have corrected my article and also referenced your comment in Reddit, in the article.

]]> /lambda-vs-proc-vs-blocks/#comment-14 Thu, 25 Aug 2016 01:49:00 +0000 https://redpanthers.co/?p=467#comment-14 The described difference in return behavior between procs and blocks is incorrect — there is no difference. In both of them, `return` returns from the method the proc/block was _defined in_. You get ‘unexpected return’ if the context the proc/block was defined in doesn’t allow return, it wasn’t in a method. But in fact they work the same.
I will demonstrate that in the following gist. Also, your examples are confusing because the statement `puts x` actually returns nil for any `x`, so `return puts x` is actually always `return nil`, although with a side effect of printing to console. In my examples I’ll avoid that.
https://gist.github.com/jrochkind/2f01ea0c8472af63ebf3da365b0852ff
Procs and blocks behave identically with regard to `return` — in both cases, the return will cause a return from the _place the proc or block was defined_, and in both cases you’ll get a LocalJumpError if that place doesn’t allow ‘return’ (because it’s not being executed as a method body).

]]>