2012/6/2 Isaac Schlueter <[email protected]>: > > However, this program will (maybe) be affected: > > process.nextTick(function f () { > process.nextTick(f) > }) > setTimeout(function () { > console.log('bar') > }, 100) > > Also, we can probably figure out a way to make it work such that it > runs the first nextTick at the end of the current RTC, but subsequent > ones at some point get deferred. As I said earlier in the thread, we > haven't investigated it thoroughly. >
If we defer subsequent calls then it's the same thing, but without the I/O window that causes bugs. I don't care if it's last or first. The idea was scary because it was suggested that this would starve the event loop and that it was OK to do that. It's black and white different, and if you need that kind of behavior, then it's better to use a new method for that.
