Re: [whatwg/streams] pipeTo() algorithm shuts down too early on readable close()? (#644)

> I guess it would be observably different in that the readable stream might become canceled sooner. Which is probably a good thing.

So, specifically, we get different behaviour when the underlying sink on the end of a pipe calls `controller.error()` without immediately rejecting the promise returned from `write()`. Back propagation starts sooner, meaning that earlier pipeTos can be rejected before that write completes. I think this doesn't matter, because

1. The call to `controller.error()` implies that the write is never going to do anything useful, however long it takes.
2. Using the normal `readable.pipeThrough(transform).pipeTo(writable)` syntax no-one is observing the result of any `pipeTo()` but the last one anyway.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/streams/issues/644#issuecomment-272772931