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

With this, we gain more precise control over the timing of abort. I'm not sure if this is something we really want. Looks over-killing at a glance.

----

Let me go back to the discussion about need for interrupting an ongoing `us.write()`. I'm okay with making `us.write()` atomic. The primary plan is to introduce the cancel token. The backup plan is maybe to that we invoke a separate callback, say `us.abortWrite()`, when there's ongoing `us.write()` while keeping `us.abort()` happen only after the ongoing `us.write()` finishes.

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