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

Ah, not so sure if I remember correctly. But let me explain more.

The concern I raised before was that even after the promise returned by `sink.close()` is fulfilled, until the fulfillment is propagated to the logic to update the state of the stream to set it to `"errored"`, `writer.abort()` is not prevented, and therefore, the sink may receive `sink.abort()` even after finishing `sink.close()` successfully. I thought that the note was originally about this concern about the very edge case. IIRC, ... domenic wrote this note and talked about not only the edge case but generally about the possiblility of `sink.abort()` invocation during `sink.close()`.

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