@wycats @littlecalculist @BrendanEich ... so they also need to be able to extend break/continue semantics
-
-
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 Disagree. Block lambdas feel like syntax and sync. Reasoning abstractly leads to wrong conclusion.1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats Concrete bit about if-else nest w/ completion value in block-lambda => if-early-return non-nest refactoring.@awbjs@littlecalculist1 reply 0 retweets 0 likes -
-
Replying to @BrendanEich
@BrendanEich@awbjs@littlecalculist I'm not finding the precise example that causes the confusion. Read all of the thread. Point me?1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats Find "Luke made a stronger point:" in http://esdiscuss.org/topic/march-24-meeting-notes#content-4 ….@awbjs@littlecalculist2 replies 0 retweets 0 likes
@BrendanEich @awbjs @littlecalculist The argument is not clearly articulated, just alluded to.
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.