Introduce setImmediate API #2056
Merged
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
knopki
reviewed
Oct 20, 2020
brusherru
approved these changes
Oct 21, 2020
evgenykochetkov
force-pushed
the
add-set-immediate-api
branch
from
f377cdc
to
1cdef36
Compare
evgenykochetkov
force-pushed
the
add-set-immediate-api
branch
from
1cdef36
to
9d87e88
Compare
This was referenced Oct 28, 2020
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.
Before, we used
setTimeout(0, ctx)to schedule evaluation of a node as soon as possible.But it would only mark node as dirty on the next millisecond and generate some unnecessary code.
setImmediateis a new API for this particular case that works faster, generates less code and occupies less RAM.