Kevin Gibbons

See older discussion in https://github.com/tc39/ecma262/issues/257. Note that both SpiderMonkey and JavaScriptCore make this an early error in strict code, so it should be safe to make this legal only in...

> this requires awareness Awareness by whom?

Maybe also `|` around nonterminals.

Ehh, I'm less enthusiastic about primitives. It's not like `null` or `"foo"` or `+0𝔽` are ambiguous, whereas some of the nonterminals and aliases can look like prose (at least at...

Thanks for the report. This is caused by the hidden text to make step numbers copyable, somehow. Also, it's not exactly "every 10 steps", it's "steps which have a 0...

Filed https://bugs.webkit.org/show_bug.cgi?id=281863. Not sure what else we can do short of UA-sniffing to disable the hidden text.

I think the default should be to accept immutable buffers. Even for APIs which write to their argument (which are rare - TextEncoder encodeInto comes to mind, but little else)...

Thanks! Web reality has the error occurring before evaluation of the RHS (try `(function(){})() = console.log(0)`), and with this PR it would happen after (specifically, [Evaluation](https://tc39.es/ecma262/multipage/ecmascript-language-expressions.html#sec-assignment-operators-runtime-semantics-evaluation) for assignment expressions will...

It was intentional that field initializers run before the constructor for base classes, and runs immediately after `super()` for derived classes. Expressions in parameter defaults are logically part of the...

If you are looking at that code it is possible you could expect those classes to behave identically, sure, because you're not thinking about the fact that `this` initialization for...