Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upFunctionDeclarationInstantiation always returns a normal completion ? #837
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
anba
Mar 6, 2017
Contributor
Agreed, c90286d should be reverted because FDI can return abrupt completions for the reasons outlined above.
|
Agreed, c90286d should be reverted because FDI can return abrupt completions for the reasons outlined above. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
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.
|
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. |
jmdyck commentedMar 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.