Re semicolons: ASI can bite whether you use semicolons or not. Either learn the rules of ASI, or use a linter that guards you against unwanted behavior.
-
-
How do you feel about making semis mandatory for class fields? That was the other option (the recommendation was a compromise) but it seemed more heavy handed than the recommendation.
-
I personally think consistency is important in a code base, so required ;s in classes in a no; codebase would not be my first choice. Reading the GH issue makes it clear TC39 thinks the ASI hazards will increase, so the warning seems like a good thing IMO.
-
Right, this is where we landed. We don't want to impose semis on no-semi users. Serious no-semi users won't listen to us anyway and have linters. Casual no-semi users (memorizers) might become aware of the new hazards through the recommendation. Might switch to linters.
-
As I was trying to point out in my original tweet, there is clearly no ill intent or motives here. It is just everyone trying to improve the language and learning experience for devs.
-
Ironically, the recommendation came from a strong desire by TC39 members (including a
@github representative strongly supporting no-semi style) to avoid making semis mandatory for fields and force no-semi users to use 'em.
End of conversation
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.