Re: [whatwg/streams] Note about underlyingSink close() method is misleading (#617)

I spoke with @tyoshino in person and here is the plan we came up with:

- Calling `writer.abort() `during `us.write()` will result in all processing being delayed until the write completes. If the write succeeds, `abort()` or `close()` will be called as normal. If the write fails, behaviour will match the resolution to #620.
- Calling `writer.abort() ` during `us.close()` will return a promise rejected with a TypeError exception.
- Calling `writer.abort()` with `state === 'closing'` will still be permitted as long as `us.close()` has not started yet.

-- 
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/617#issuecomment-262890195