@littlecalculist @natefaubion @havvy @sebmarkbage @jorendorff @stv_kn @awbjs Find "wrong return" in http://esdiscuss.org/topic/march-24-meeting-notes#content-4 …, from @lukehoban.
-
-
Replying to @BrendanEich
@BrendanEich@littlecalculist@natefaubion@havvy@sebmarkbage@jorendorff@stv_kn@awbjs@lukehoban Arguments against TCP here very weak1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@BrendanEich@natefaubion@havvy@sebmarkbage@jorendorff@stv_kn@awbjs@lukehoban the topic deserves another go round3 replies 0 retweets 0 likes -
Replying to @littlecalculist
@littlecalculist@wycats@BrendanEich@natefaubion@havvy@sebmarkbage@jorendorff@stv_kn@lukehoban let it rest, get ES6 useage experience4 replies 0 retweets 0 likes -
Replying to @awbjs
@awbjs@littlecalculist@BrendanEich Will let it rest, but I think this was an extremely unfortunate decision. Predates me by mere months :(1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@littlecalculist@BrendanEich we tried hard, was nearly in spec, but really not a very good fit to JS. Lots of corner cases4 replies 0 retweets 0 likes -
Replying to @awbjs
@awbjs@littlecalculist@BrendanEich Dynamic error when used off-stack is not as bad as it seems.1 reply 0 retweets 0 likes -
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
@awbjs @littlecalculist @BrendanEich "need", non-obvious. Control structures without extensible break/continue > arrows.
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.