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

FunctionDeclarationInstantiation always returns a normal completion ? #837

Closed
jmdyck opened this Issue Mar 5, 2017 · 2 comments

Comments

Projects
None yet
3 participants
@jmdyck
Collaborator

jmdyck commented Mar 5, 2017

Commit c90286d says that FunctionDeclarationInstantiation always returns a normal completion, and inserts '!' in front of two invocations of it (here and here).

Presumably this assertion is not true in general, since FDI has calls to IteratorBindingInitialization that are prefixed by '?'.

If the intent was merely that those two invocations always return normally, then:
(a) What causes that to be true?
(b) The if-then-else following each invocation could be simplified, since it tests whether the result of FDI is abrupt.

@anba

This comment has been minimized.

Show comment
Hide comment
@anba

anba Mar 6, 2017

Contributor

Agreed, c90286d should be reverted because FDI can return abrupt completions for the reasons outlined above.

Contributor

anba commented Mar 6, 2017

Agreed, c90286d should be reverted because FDI can return abrupt completions for the reasons outlined above.

@jmdyck

This comment has been minimized.

Show comment
Hide comment
@jmdyck

jmdyck Mar 6, 2017

Collaborator

Note that simply reverting that commit will leave one of the invocations with a '?' prefix, which doesn't make sense given the if-then-else that follows. I believe the proper fix is to delete both '!' prefixes.

Collaborator

jmdyck commented Mar 6, 2017

Note that simply reverting that commit will leave one of the invocations with a '?' prefix, which doesn't make sense given the if-then-else that follows. I believe the proper fix is to delete both '!' prefixes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment