Of those new examples, the worst one isn't fixed by always using semicolons. I can see people trying to put `async` on a separate line, especially once decorators get in.
-
-
Replying to @spion @lucasazzola and
That issue would have been fixed by making semis mandatory in classes, which is perhaps what we should have done.
1 reply 0 retweets 2 likes -
Replying to @wycats @lucasazzola and
Perhaps TC39 should make that a recommendation to themselves then
2 replies 0 retweets 0 likes -
The recommendation is very specific about what/when things occur and provides an actionable task. Is there any way we can reword it to be better while preserving these listings and having an actionable task for them?
1 reply 0 retweets 0 likes -
Replying to @bradleymeck @wycats and
The only actionable task that really helps is to use a tool that detects these issues or for implementers to add warnings for unexpected ASI in engines (like return/break and now async methods)
2 replies 0 retweets 2 likes -
Replying to @spion @bradleymeck and
As a user of prettier, I don't intend to follow the current recommendation. With prettier unexpected ASI non-insertions are more obvious than unexpected ASI insertions, as it moves the entire expression to the line above (super obvious when it happens)
1 reply 0 retweets 2 likes -
Replying to @spion @bradleymeck and
Unexpected ASI insertions manifest as an invisible tiny little ";" being added at the end of the line. Quite difficult to notice.
1 reply 0 retweets 0 likes -
Replying to @spion @bradleymeck and
True, but either way Prettier will make it more obvious. To me it makes sense for ASI hazards to be documented in the spec, but use of semis should be a matter of preference.
1 reply 0 retweets 0 likes -
Replying to @lucasazzola @spion and
Let's face it, people new to JS don't read the spec, and experienced devs who like one style won't be swayed by a recommendation to the contrary.
1 reply 0 retweets 1 like -
Replying to @lucasazzola @bradleymeck and
No, what will happen is that all nuance of the recommendation will get lost through blog posts and the message will become "Always use semicolons and it will be ok, its recommended by the standard."
2 replies 0 retweets 0 likes
"the JavaScript standard" conflicts with "standard js" so there's at least that. 
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.