Re: [whatwg/streams] pipeTo(): Rationale for not making shutdown() no-op when shuttingDown is set (#557)

So my main concern is that with pipeTo, we are trying to do something different from normal and spec the observable semantics only. If we start getting too algorithmic we may get in the way of that. The existing algorithmic bookkeeping is meant to capture aspects of the shutdown sequence that are hard to specify otherwise.

So if we have bugs, we need to fix them. But for any other such changes, if they are not observable, then I think we should lean toward simplicity. I'm having a bit of a hard time figuring out which this is and would appreciate your help there.

-- 
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/557#issuecomment-256151458