@littlecalculist @natefaubion @havvy @sebmarkbage @jorendorff @stv_kn @awbjs Find "wrong return" in http://esdiscuss.org/topic/march-24-meeting-notes#content-4 …, from @lukehoban.
@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". -
@wycats ISTM you're doing the "blub" thing as a recovering Rubyist. Look at if-else-value nest vs. if-return case.@awbjs@littlecalculist -
@BrendanEich@awbjs@littlecalculist ISTM that committee did not consider `continue` or something like it as "return from block" a la Ruby -
@wycats Of course we did; we're not idiots, we looked at Ruby. JS has no next v. continue. You're "blubbing" here.@awbjs@littlecalculist -
@BrendanEich@awbjs@littlecalculist "we're not idiots; we looked at ruby" does not comport with my experience on TC39 - 4 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.