@wycats @stefanpenner To be precise, I'm proposing that labels at the beginning of `=>` blocks be syntax errors. (thanks @terzicigor)
-
-
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@jo_liss@stefanpenner Yeah, since strict mode (prior to ES6 modules) is underused, might well fly.1 reply 0 retweets 0 likes -
Replying to @BrendanEich
@BrendanEich@jo_liss@stefanpenner it's underused *especially* by people who do crazy things like cargo cult `javascript:` into a program1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@jo_liss@stefanpenner not cargo cult AFAIK -- just copy-paste and concatenation.1 reply 0 retweets 1 like -
Replying to @BrendanEich
@wycats@jo_liss@stefanpenner 1/ Context-blindness if not copy/paste helped people write onclick=`javascript:...` too. Again copy-paste is1 reply 0 retweets 0 likes -
Replying to @BrendanEich
@wycats@jo_liss@stefanpenner 2/ most parsimonious explanation, because in Netscape 2 some elements lacked onclick but had href= or src=.4 replies 0 retweets 0 likes
@BrendanEich @jo_liss @stefanpenner time is short here because of the impending module normalization of strict mode
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.