[whatwg/streams] Should writableStream.abort() reject on already-errored streams? (#900)

As noted in #847, this can lead to lots of redundant `.catch(() => {})`s.

I think it's especially strange that this rejects given that we just resolve with undefined if the stream is already _closed_. If anything that's the case where you failed to abort. If you're already _errored_, then you've basically aborted the stream already.

So I'm inclined to change this. Any thoughts?

-- 
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/900

Received on Thursday, 8 March 2018 05:31:44 UTC