You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example, do { ; } has a completion value of { [[Type]]: normal, [[Value]]: empty, [[Target]]: empty }. But empty is not a value which can actually be used in an expression. That case needs to be handled explicitly, as in step 27 of PerformEval:
If result.[[Type]] is normal and result.[[Value]] is empty, then
a. Set result to NormalCompletion(undefined).
The text was updated successfully, but these errors were encountered:
The do expression do {} needs to evaluate to [[Type]]: normal, [[Value]]: empty so it has Tennant's correspondence with { } when used in a statement context.
I disagree with this; I think it's fine for (do { 0; (do {}); }) to be undefined instead of 0, despite the Tennant's correspondence violation.
For example,
do { ; }
has a completion value of{ [[Type]]: normal, [[Value]]: empty, [[Target]]: empty }
. Butempty
is not a value which can actually be used in an expression. That case needs to be handled explicitly, as in step 27 of PerformEval:The text was updated successfully, but these errors were encountered: