Re: [whatwg/streams] Do not allow abort() to interrupt a closing writable stream? (#632)

IIRC, the note was about possible invocation of both `sink.close()` and `sink.abort()` on the same sink due to that completion of `sink.close()` is processed and reflected to the state of the stream asynchronously and until that happens `sink.abort()` is not rejected. So, this is no longer the case. Once `sink.close()` is called, `[[inClose]]` is set to **true** to delay `writer.abort()` execution and then it never invokes `sink.abort()`.

-- 
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/632#issuecomment-274735208