Skip to content
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.

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

Editorial: Remove erroneous handling of RETURN completion type #399

Merged
merged 1 commit into from
Feb 13, 2024

Conversation

ptomato
Copy link
Collaborator

@ptomato ptomato commented Feb 13, 2024

ECMA-262 Call, and therefore OrdinaryWrappedFunctionCall, can only return completions of type NORMAL or THROW. All other types such as RETURN are wrapped inside the various objects' [[Call]] internal methods. Therefore handling the RETURN completion type here was erroneous and had no effect.

Similarly, the editors note about different completion types also had no effect.

Closes: #371

ECMA-262 Call, and therefore OrdinaryWrappedFunctionCall, can only
return completions of type ~normal~ or ~throw~. All other types such as
~return~ are wrapped inside the various objects' [[Call]] internal
methods. Therefore handling the ~return~ completion type here was
erroneous and had no effect.

Similarly, the editors note about different completion types also had
no effect.

Closes: tc39#371
@ptomato ptomato requested a review from caridy February 13, 2024 01:07
@ptomato
Copy link
Collaborator Author

ptomato commented Feb 13, 2024

cc @linusg

Copy link
Member

@linusg linusg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

@caridy caridy merged commit fa39ea4 into tc39:main Feb 13, 2024
@ptomato ptomato deleted the 371-completion-types branch February 13, 2024 16:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Incorrect result handling in "2.1 [[Call]]"?
3 participants