Skip to content

Editorial: replace ReturnIfAbrupt with ? shorthand #254

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nicolo-ribaudo merged 1 commit into from
May 19, 2026
Merged

Editorial: replace ReturnIfAbrupt with ? shorthand #254

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions spec.emu
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -211,14 +211,14 @@
</emu-clause>
</blockquote>

<p>All calls to abstract operations that return completion records are implicitly assumed to be wrapped by a ReturnIfAbrupt macro, unless they are explicitly wrapped by an explicit Completion call. For example:</p>
<p>All calls to abstract operations that return completion records are implicitly assumed to be wrapped by ECMA-262's `?` <a href="https://tc39.es/ecma262/#sec-shorthands-for-unwrapping-completion-records">shorthand for unwrapping completion records</a>, unless they are wrapped by an explicit Completion call. For example:</p>
<emu-alg example>
1. Let _result_ be GetTheAnswer(_value_).
1. Let _second_ be Completion(GetTheAnswer(_value_)).
</emu-alg>
<p>is equivalent to:</p>
<emu-alg example>
1. Let _result_ be ReturnIfAbrupt(GetTheAnswer(_value_)).
1. Let _result_ be ? GetTheAnswer(_value_).
1. Let _second_ be Completion(GetTheAnswer(_value_)).
</emu-alg>
</emu-clause>
Expand Down
Loading