You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Intuitively, I thought this would be supported, the same way that a Promise that resolves to a Promise waits for both.
Now that async/wait is supported in node, I'd say the case for supporting this is even stronger, take for example (very abstract, I know, but I'm sure you too can see a real world use case for this):
Sure, done. While I was at it, I noticed that because of the promise, all errors in the start callback were swallowed by the promise. Would it be desirable to run process.nextTick around the done.call in runTask to avoid that?
Is there any particular reason why promises that resolve to a stream aren't supported? For example:
Intuitively, I thought this would be supported, the same way that a Promise that resolves to a Promise waits for both.
Now that async/wait is supported in node, I'd say the case for supporting this is even stronger, take for example (very abstract, I know, but I'm sure you too can see a real world use case for this):
Currently I'm using node-promisepipe to work around this, but I think this could be supported natively. Thoughts?
The text was updated successfully, but these errors were encountered: