Re: [whatwg/streams] [WritableStream] Shouldn't the state after writer.abort() be closed? (#464)

Hmm, yeah. I remembered that we agreed on that abort() should play the role of having a writable stream pretend to be errored by itself for the externally-provided reason. But I thought that it was backed by the demand to implement the way to abort pipeTo() operation and propagating error to both direction. It's gone.

---
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/464#issuecomment-223197040