Anatoli Papirovski e7af9830e9 timers: run nextTicks after each immediate and timer ... In order to better match the browser behaviour, run nextTicks (and subsequently the microtask queue) after each individual Timer and Immediate, rather than after the whole list is processed. The current behaviour is somewhat of a performance micro-optimization and also partly dictated by how timer handles were implemented. PR-URL: https://github.com/nodejs/node/pull/22842 Fixes: https://github.com/nodejs/node/issues/22257 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Gus Caplan <me@gus.host> Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>		2018-10-17 20:38:07 -07:00
..
immediate.js
set-immediate-breadth-args.js
set-immediate-breadth.js
set-immediate-depth-args.js
timers-breadth.js
timers-cancel-pooled.js
timers-cancel-unpooled.js
timers-depth.js
timers-insert-pooled.js
timers-insert-unpooled.js
timers-timeout-nexttick.js	timers: run nextTicks after each immediate and timer	2018-10-17 20:38:07 -07:00
timers-timeout-pooled.js
timers-timeout-unpooled.js