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

I think I would be OK with (iii). Changing it to a TypeError saying that the stream is aborted seems good. In the future we can consider adding a `.reason` property if people want it, although thinking about it, I kind of doubt they will.

I don't recall any discussions about that in Promise.all, yeah. It's more just, signaling what caused the process to fail. I think in most use cases of exceptions you need to put enough information in the exception (or implicitly in its stack trace, which is usually saved at creation time) to allow people to diagnose the problem.

I think we agree that cancelation as success was not super-great for readable streams. Maaaaybe if cancelable promises get through, and we add use counters showing people rarely reach the fulfillment handler for closed on a canceled stream, we could change it. But likely it will just be a small design wart.

---
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-229132641