process: slight refinements to nextTick#17421
Closed
Uh oh!
There was an error while loading. Please reload this page.
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.
A couple of very slight refinements to
process.nextTick& its supporting code.lengthprop onNextTickQueueclass. We technically don't need to keep track of the length of the queue in two places as we already havetickInfodoing that work (between the index & the length we have enough data for everything).asyncIdin a const within the_tickCallbackfunction. Accessing symbol properties seems to be quite a bit more expensive than string keys so this actually has a decent performance impact.Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passesAffected core subsystem(s)
process