This repository has been archived by the owner on Aug 29, 2021. It is now read-only.
Revisit suspending the running execution context for modules, fixes #143 #175
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.
Tries to address #143 -- my reading of the spec is that, we should not be suspending the execution context in the case of an async module. The async module context plays the same role as the copy of the running context,
asyncContext
does in AsyncFunctionStart, and the running context in that case is not suspended. I believe it would be wrong to suspend in the case of modules, as execution should continue and the module context itself should be treated as a promise from my understanding.