Editorial: Explicitly track async evaluation order of pending modules #3353
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
nicolo-ribaudo
changed the title
nicolo-ribaudo
force-pushed
the
async-evaluation-order
branch
2 times, most recently
from
d600852 to
f96a304
Compare
syg
reviewed
Jun 21, 2024
nicolo-ribaudo
force-pushed
the
async-evaluation-order
branch
2 times, most recently
from
4cdd981 to
b1c782e
Compare
|
PR updated, sorry I forgot about this. For #3353 (comment), I pushed it in a second commit to make it easier to review where I'm using |
nicolo-ribaudo
force-pushed
the
async-evaluation-order
branch
from
d5527c1 to
0789693
Compare
bakkot
reviewed
Feb 21, 2025
bakkot
approved these changes
Feb 21, 2025
There was a problem hiding this comment.
LGTM with my comment. This is so much nicer, thanks.
Don't forget to update https://tc39.es/proposal-defer-import-eval/#sec-example-cyclic-module-record-graphs-deferred-imports after this lands.
jmdyck
previously requested changes
Feb 22, 2025
michaelficarra
approved these changes
Mar 5, 2025
|
Ready except it needs the Edit: I went ahead and did this myself. |
bakkot
added
ready to merge
…tc39#3353) The execution order of modules that were waiting on a given async module was based on the order in which their [[AsyncEvaluation]] field was set to *true*. This PR replaces the [[AsyncEvaluation]] boolean with an actual number that keeps track of ordering in each agent. It also adds a note on when it's safe to reset this order to 0, since: - implementations might want to prevent this number from overflowing, and V8 currently has a bug that resets the number to 0 too early - figuring out when it's safe to reset the number might not be trivial, given the complexity of the module algorithms.
ljharb
force-pushed
the
async-evaluation-order
branch
from
ca9388f to
030dcd6
Compare
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.
The execution order of modules that were waiting on a given async module was based on the order in which their [[AsyncEvaluation]] field was set to true.
This PR replaces the [[AsyncEvaluation]] boolean with an actual number that keeps track of ordering in each agent. It also adds a note on when it's safe to reset this order to 0, since:
You can verify the numbers in the updated tables for the example using https://nicolo-ribaudo.github.io/es-module-evaluation/.
Fixes #3289