This post gets to the core of my ultimate concern https://mail.mozilla.org/pipermail/es-discuss/2012-January/019520.html … The basic problem was that BL-based ctl abstraction are leaky...
-
-
Read closely, justifications strong. No way: dynamic throw-like return/break/continue. Static better but dead frame return throws hazardous.
-
You have to do better than "return from dead frame hazardous" when Ruby has the same hazard and doesn't create too much confusion.
-
Is it possible to describe in reasonably lay terms why this is harder for JS than Ruby? Both are dynamically typed, right?
-
You won't find a good answer other than Blub.
-
The arguments the experienced folks (in good faith, and honestly) used to kill block lambdas in JS apply to Ruby too.
-
I don't mean that
@BrendanEich or@awbjs were blubbing. I mean others were and persuaded them to live with these arguments to kill it. -
And honestly, this is how consensus works. I wasn't around yet, and vastly prefer arrows and no-block-lambdas to deadlock.
-
The arguments against block lambdas weren't persuasive to me, but between committee members blubbing and good enough arguments, yolo.
- 5 more replies
New conversation -
-
-
The decision is made. That's, in practice, enough. We're not gonna have arrows and block lambdas.
-
Yes done deal. Mostly showing that considerable thought+experience preceded decisions.
-
I don't buy the idea that JS is *so* different from Smalltalk and Ruby. Ruby has C-style control flow too.
-
Ruby has lambda vs http://Proc.new gratuitous split. Also Ruby far from static C in semantics. I gave Block Lambdas my best shot.
-
Gratuitous split but maybe worth it.
-
Unfalsifiable faith-article. Consider C switch fall through hazard, real world comp.risks cost. Ruby dead frame return throw bug experience?
-
Very little dead frame return issues. Has to do with whether you're taught blocks as functions or something else.
-
Dead frames not the problem. Instead a layering issue wrt nested user and language defined ctl abstractions. Some day I'll show you
- 7 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.