Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upPossibly-unreachable specification text #299
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
anba
Jan 19, 2016
Contributor
These steps were initially added to support do-expressions, but currently they aren't needed (and got removed in 748ec83).
|
These steps were initially added to support do-expressions, but currently they aren't needed (and got removed in 748ec83). |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
@anba Thank you! |
jugglinmike
closed this
Jan 19, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
anba
Jan 19, 2016
Contributor
(BTW there is a similar issue in CreatePerIterationEnvironment: lastIterationEnvRec.GetBindingValue can never return an abrupt completion in ES2015/2016. The call to ReturnIfAbrupt was only added to handle this case: for (let x = do { continue; }; ;) {}. )
|
(BTW there is a similar issue in CreatePerIterationEnvironment: |
jugglinmike commentedJan 19, 2016
I'm having trouble verifying step 4.a.ii.1 in section 13.12.9 ("Runtime Semantics: CaseBlockEvaluation"):
source: http://www.ecma-international.org/ecma-262/6.0/#sec-runtime-semantics-caseblockevaluation
(The algorithm for blocks containing the
defaultcase have an equivalent step.)Because CaseSelectorEvaluation is defined as follows:
...the question I'm having trouble answering is: which Expression will return an empty abrupt completion?