I tried out "automatic comma insertion" on some real-world code examples; in my
opinion it decreases code readability.It solves the problem of needing to
change two lines when adding to the end of a list, but that already has many
solutions (the awful comma-first style, allowing trailing commas, just deal
with it, syntax-aware diff).
On Tuesday, September 12, 2017, 3:09:51 PM CDT, dante federici
<c.dante.feder...@gmail.com> wrote:
I mean, it's the general case of the "get" and "set" when defining a
method:https://www.ecma-international.org/ecma-262/6.0/#sec-method-definitions-runtime-semantics-propertydefinitionevaluation
That being said, there's a lot of "you just shouldn't do that" in javascript.
Looking at you, `undefined` not being a reserved word.
Syntax aside, a question that hasn't been sufficiently answered is what value
does this actually add other than "I don't want to type ,"? Arguments for
"easier to read code" I would absolutely disagree with, since it may be easier
for one person, but not another. Giving a "line break matters" is a terrible
answer, since that would break a ton of backwards
compatibility._______________________________________________
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
_______________________________________________
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
