Re: [whatwg/streams] Propagate errors from writableStream.abort(reason) (#896)

I found the original thread; digesting now: https://github.com/whatwg/streams/issues/464

One alterative it brings up is having pipeTo do error propagation, even if abort() does not. That would mean using e.g. WritableStreamDefaultControllerError instead of WritableStreamAbort. That's a bit of a layering violation in our current setup because currently only the creator of the writable stream can use WritableStreamDefaultControllerError. But maybe we can rearrange things to justify to ourselves.

-- 
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/896#issuecomment-371385812