Skip to content

Commit

Permalink
Editorial: insert '!' and '?'
Browse files Browse the repository at this point in the history
In PR $1571:

https://github.com/tc39/ecma262/pull/1571/files#diff-3540caefa502006d8a33cb1385720803L19940
removed the step
"Assert: _constructorInfo_ is not an abrupt completion."
but didn't insert the equivalent "!" on the previous line.

https://github.com/tc39/ecma262/pull/1571/files#diff-3540caefa502006d8a33cb1385720803L23362
removed a ReturnIfAbrupt step,
but didn't insert the equivalent '?' in the previous line.
  • Loading branch information
jmdyck committed Sep 9, 2019
1 parent 133dc35 commit f8256fe
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions spec.html
Original file line number Diff line number Diff line change
Expand Up @@ -19961,7 +19961,7 @@ <h1>Runtime Semantics: ClassDefinitionEvaluation</h1>
<pre><code class="javascript">constructor() {}</code></pre>
using the syntactic grammar with the goal symbol |MethodDefinition[~Yield, ~Await]|.
1. Set the running execution context's LexicalEnvironment to _classScope_.
1. Let _constructorInfo_ be DefineMethod of _constructor_ with arguments _proto_ and _constructorParent_.
1. Let _constructorInfo_ be ! DefineMethod of _constructor_ with arguments _proto_ and _constructorParent_.
1. Let _F_ be _constructorInfo_.[[Closure]].
1. If |ClassHeritage_opt| is present, set _F_.[[ConstructorKind]] to `"derived"`.
1. Perform MakeConstructor(_F_, *false*, _proto_).
Expand Down Expand Up @@ -23379,7 +23379,7 @@ <h1>Runtime Semantics: Evaluation</h1>
</emu-alg>
<emu-grammar>ExportDeclaration : `export` `default` ClassDeclaration</emu-grammar>
<emu-alg>
1. Let _value_ be BindingClassDeclarationEvaluation of |ClassDeclaration|.
1. Let _value_ be ? BindingClassDeclarationEvaluation of |ClassDeclaration|.
1. Let _className_ be the sole element of BoundNames of |ClassDeclaration|.
1. If _className_ is `"*default*"`, then
1. Let _env_ be the running execution context's LexicalEnvironment.
Expand Down

0 comments on commit f8256fe

Please sign in to comment.