Re: [whatwg/streams] pipeTo(): Rationale for propagating an error happened during error propagation to pipePromise (#558)

> To me the abort(err) handler is kind of like a catch-and-rethrow clause. By default it will "rethrow" the error passed in. But since error2 is encountered while handling error1, the outer caller (i.e. the caller of pipeTo) instead sees error2.

This is an interesting view point and would help get convinced on the design though it's limited to the cases where `ReadableStreamCancel()`, `WritableStreamAbort()` successfully invoke `underlyingSource.cancel()`, `underlyingSink.abort()`.

Thanks Domenic. I'll close this issue for now.

Anyone who finds this behavior inconvenient, unclear, etc., please comment on this issue with your opinion so that we can revisit it.

-- 
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/558#issuecomment-258354966