Consider using `setImmediate` if available about q HOT 2 CLOSED

I like setImmediate. I’ve experimented with shimming it and using it, but it does not make sense to shim it in Q.

Part of this is that nextTick(cb) is the only part of the signature we need and nextTick does not have to implement handle tracking or variadic argument forwarding like setImmediate(cb(...args), ...args):handle. It would be a waste of both weight and performance to properly shim setImmediate. I would even use a global nextTick before considering using a global ``setImmediate because of this consideration.

var nextTick = global.nextTick || global.setImmediate || nextTickShim;

I do want to axe the enqueue module dependency. It is a legacy from Narwhal, which I think we should leave behind.

In the nextTick shim, I would also like to empty the queue in a single event to speed things up and make some diagnostics less noisy.

from q.

Yeah, the fact setImmediate has all the unnecessary stuff is unfortunate.

So your proposal is to change to

var nextTick = global.nextTick || global.setImmediate ||
               (typeof process !== "undefined" && process.nextTick) ||
               nextTickShim;

and then, perhaps in the future, publish a browser-based global.nextTick library?

from q.