Move DisposeResources to Evaluation of FunctionStatementList #178
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 moves the
DisposeResources
calls from the abstract closures inEvaluateFunctionBody
,GeneratorStart
,AsyncGeneratorStart
, andAsyncBlockStart
to theEvaluation
ofFunctionStatementList
. This centralizes the disposal logic for all function types and avoids the complexity of handling functions created from Abstract Closures that do not currently establish a proper declarative environment.This change is based on findings discovered while writing Test262 tests and implementing this proposal in Engine262.
Fixes #176
Fixes #177
cc: @tc39/ecma262-editors