-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrapping everything in nextTick() should be optional #29
Comments
The purpose of calling It’s relatively straightforward to safely handle a readable stream in conjunction with promises. https://github.com/kriskowal/q-io/blob/master/q-io.js#L13-100 (Needs further work to support throttling, but has been indispensable for my stack.) |
Yes, running callbacks on stack is not preferable for flow control module, I agreed. But can you please point me to any place where such |
Thanks. The documentation needs another pass for clarity, for sure. excerpt:
|
Now tracking as #31. |
Calling
nextTick
is good for letting other parts of application to execute, but it may cause nonobvious problems when dealing with streams in node.js.For example, creating ReadStream and then using it after
resolve
will end up in skipping some"data"
events on it, because we skipped one event-loop tick.The text was updated successfully, but these errors were encountered: