This is where engines need to spend a lot of effort to make arrays fast despite the terrible semantics, which are completely counterintuitive to developers anyways. Fortunately TypedArrays at least get this right.
-
-
No. Find "In my humble opinion" in https://esdiscuss.org/topic/excluding-features-from-sloppy-mode#content-109 …. Andreas wanted new syntax only in strict, or else in sloppy w/o implicit "micro-mode" strict (1JS).
-
Who was the micromode champion. I remember having to argue somewhat forcefully against them.
-
Topic is complex: supporting new syntax in sloppy mode begs questions, e.g. are duplicate formals allowed if you use rest or destructuring? Is an early error against dups a micromode? (No.)
-
Opting into strict for the function body is a micromode. New rules that only affect parameters is not (but I'm generally concerned about refactoring hazards)
-
Static checks for early errors aren’t micromodes either, in my book.
-
Turning code with well defined semantics into an error because of a seemingly unrelated refactor (switching from `arguments` to `...args`) is definitely a micromode.
-
Agreed, I’m not talking about what we agreed not to do, rather about destructuring params forbidding dup names, e.g.
-
Yeah, that kind of thing is generally fine.
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.