Normative: Restrict completion values callables can return #2448
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
syg
added
normative change
bakkot
approved these changes
Jul 1, 2021
michaelficarra
approved these changes
Jul 8, 2021
ljharb
added
has consensus
michaelficarra
added
the
ready to merge
ljharb
force-pushed
the
restrict-callables
branch
from
5bdde7e
to
c8ee518
Compare
mathiasbynens
pushed a commit
to mathiasbynens/ecma262
that referenced
this pull request
Oct 18, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This normatively constrains implementations to not have functions return control-flow altering completions other than
~throw~. I expect nailing this down to be both a universal truth in all implementations and uncontroversial: calling a function shouldn't be able to e.g. break out of a loop.