jmdyck
jmdyck
In translation.md, you have both: ``` emit(load_attr!, ...) emit(store_attr!, ...) emit(store_subscr!) ``` and: ``` emit(LOAD_ATTR, ...) emit(STORE_ATTR, ...) emit(STORE_SUBSCR) ``` Do these two forms mean different things?
E.g., change: > 1. Return the BoundNames of |Foo|. to: > 1. Return BoundNames of |Foo|. ---- This PR is divided into 4 commits, depending on: - whether the occurrence...
([This recent comment](https://github.com/tc39/ecma262/issues/3314#issuecomment-2067414362) from @michaelficarra reminded me of [this old comment](https://github.com/tc39/ecma262/pull/2592#issuecomment-981231972) from me. It didn't get any discussion at the time (it wasn't crucial to the PR), so I'm raising...
In 20.3.1.16 "Date Time String Format", in the table, some of the explanations are sans-serif and some are serif. (In the PDF, they're all sans-serif.)
There are a few places where the spec should use `...` but instead has `...`: 18.2.6.1 / Runtime Semantics B.1.1 / Static Semantics B.1.4 / Syntax B.1.4 / Pattern Semantics...
This PR completes a small bugfix from 9 years ago. Fixes #2663. ---- History: 2015-07-17: @bakkot identifies a problem in Annex B's "Changes to FunctionDeclarationInstantiation": https://esdiscuss.org/topic/block-level-function-declarations-web-legacy-compatibility-bug To remedy this, @allenwb...
In the definition for "suspending function", the execution context `context` has a "state" that is either **Suspended** or **Active**[`caller`]. Where is all this defined? I know that the ECMAScript spec...
At the editor call today, there was discussion about capitalizing spec type names. Here's a list of 'type names' (for some definition of that idea) that have at least one...