@littlecalculist Didn't blocks fall in part b/c JS's C-stmt heritage hates TCP? @natefaubion @havvy @sebmarkbage @jorendorff @stv_kn @awbjs
@awbjs @littlecalculist @BrendanEich Will let it rest, but I think this was an extremely unfortunate decision. Predates me by mere months :(
-
-
@wycats@littlecalculist@BrendanEich we tried hard, was nearly in spec, but really not a very good fit to JS. Lots of corner cases -
@awbjs@littlecalculist@BrendanEich Dynamic error when used off-stack is not as bad as it seems. -
@wycats@littlecalculist@BrendanEich I know ST block/return semantics well. But break/continue adds whole new dimension of issues. -
@awbjs@littlecalculist@BrendanEich We can chat over beer :) I would expect break/continue to unwind back to lexical loop. -
@wycats@littlecalculist@BrendanEich ... so they also need to be able to extend break/continue semantics -
@awbjs@littlecalculist@BrendanEich Again, certainly better than arrows. -
@wycats@littlecalculist@BrendanEich It's slowly coming back to me. Labels were another issue. If you're going to do it, do it right. -
@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" - 10 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.