@wycats @stefanpenner May not be possible to make it an object because () => {} can't change, but surely error is better than silent label?
-
-
Replying to @jo_liss
@wycats@stefanpenner Seems like pretty big footgun; fails silently, and most people don't even know labels are a thing. /via@briancavalier3 replies 0 retweets 1 like -
Replying to @jo_liss
@wycats@stefanpenner To be precise, I'm proposing that labels at the beginning of `=>` blocks be syntax errors. (thanks@terzicigor)3 replies 0 retweets 2 likes -
Replying to @jo_liss
@wycats@stefanpenner Hey@BrendanEich, I liked your strawman in https://esdiscuss.org/topic/x-foo-bar with UnlabeledStatement, disallowing () => {x: y}.2 replies 0 retweets 0 likes -
Replying to @jo_liss
@jo_liss@stefanpenner@BrendanEich I like it too. Let's do it.2 replies 0 retweets 3 likes -
Replying to @wycats
@wycats@jo_liss@stefanpenner We know of stray labels in Web JS, especially "javascript:" (in mid-file even). Worth a revival post, thanks.1 reply 0 retweets 0 likes -
Replying to @BrendanEich
@BrendanEich@jo_liss@stefanpenner Could it be retrofitted onto strict mode? Might be web compat.4 replies 0 retweets 0 likes -
Replying to @wycats
@wycats@BrendanEich@jo_liss@stefanpenner My spidey sense is unclear on whether it might even fly for the whole web, not just strict mode.1 reply 0 retweets 0 likes -
Replying to @littlecalculist
@littlecalculist@BrendanEich@jo_liss@stefanpenner the javascript: issue seems plausible.1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@littlecalculist@BrendanEich@jo_liss@stefanpenner wouldn't arrows be new code, thus likely to be fixed quickly?1 reply 0 retweets 0 likes
@ljharb @littlecalculist @BrendanEich @jo_liss @stefanpenner We could definitely do it for just arrows, but maybe we can do better
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.