Use setImmediate when available instead of process.nextTick #6

Open
wants to merge 1 commit into
from

Conversation

Projects
None yet
2 participants

process.nextTick preempts IO, so in almost all cases setImmediate is preferred.

@wibblymat wibblymat Use setImmediate when available instead of process.nextTick
process.nextTick preempts IO, so in almost all cases setImmediate is preferred.
7529474

This looks OK to me. Let me know how can I help to get this pull request merged in a new version of chainsaw.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment