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?
1 reply 0 retweets 1 like -
Replying to @BrendanEich @awbjs and
Very little dead frame return issues. Has to do with whether you're taught blocks as functions or something else.
1 reply 0 retweets 2 likes -
Replying to @wycats @BrendanEich and
Dead frames not the problem. Instead a layering issue wrt nested user and language defined ctl abstractions. Some day I'll show you
1 reply 0 retweets 0 likes -
Replying to @awbjs @BrendanEich and
I know the issue about `break` needing N frames depending on how layered the abstraction is. Is that what you mean?
1 reply 0 retweets 0 likes -
Replying to @wycats @BrendanEich and
Not a matter of frame counting b/c block creation site does know nature or depth of ctl abstraction function impl.
2 replies 0 retweets 0 likes -
Replying to @awbjs @BrendanEich and
Right. I agree this is a wart. Doubt it's fatal.
1 reply 0 retweets 0 likes -
break should break (like exception) to a unique labelled continuation, created for each block. continue should return the block.
2 replies 0 retweets 0 likes -
iow break is like a smaller-scoped return. Both can desugar into an escape continuation with appropriate scope.
2 replies 0 retweets 0 likes -
I'll hold off future attempts to probe until the next time we meet in person :)
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.