@littlecalculist I'm recalling http://esdiscuss.org/topic/march-24-meeting-notes#content-4 …. What errors did you mean? @natefaubion @havvy @sebmarkbage @jorendorff @stv_kn @awbjs
@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" -
@wycats No, see Luke Hoban's point. JS is statement-full. Adding block lambdas late makes wrong return bug habitat.@awbjs@littlecalculist -
@BrendanEich@awbjs@littlecalculist This argument is ~ "blub". - 8 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.