@awbjs @littlecalculist @BrendanEich Dynamic error when used off-stack is not as bad as it seems.
-
-
Replying to @wycats
@wycats@littlecalculist@BrendanEich I know ST block/return semantics well. But break/continue adds whole new dimension of issues.1 reply 0 retweets 0 likes -
Replying to @awbjs
@awbjs@littlecalculist@BrendanEich We can chat over beer :) I would expect break/continue to unwind back to lexical loop.2 replies 0 retweets 0 likes -
Replying to @wycats
@wycats@littlecalculist@BrendanEich ... so they also need to be able to extend break/continue semantics4 replies 0 retweets 0 likes -
Replying to @awbjs
@awbjs@littlecalculist@BrendanEich Again, certainly better than arrows.1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@littlecalculist@BrendanEich It's slowly coming back to me. Labels were another issue. If you're going to do it, do it right.2 replies 1 retweet 1 like -
Replying to @awbjs
@awbjs@littlecalculist@BrendanEich It seems like you said "if you're gonna do it, do it right" and others said "nah, seems weird and hard"3 replies 0 retweets 0 likes -
Replying to @wycats
@wycats No, see Luke Hoban's point. JS is statement-full. Adding block lambdas late makes wrong return bug habitat.@awbjs@littlecalculist2 replies 0 retweets 1 like -
Replying to @BrendanEich
@BrendanEich@awbjs@littlecalculist This argument is ~ "blub".2 replies 0 retweets 0 likes -
Replying to @wycats
@wycats ISTM you're doing the "blub" thing as a recovering Rubyist. Look at if-else-value nest vs. if-return case.@awbjs@littlecalculist6 replies 0 retweets 0 likes
@BrendanEich @awbjs @littlecalculist However, there is a similar pathology common in Lispers; "must have this feature or lang is crippled"
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.