- From: Domenic Denicola <notifications@github.com>
- Date: Mon, 15 May 2017 16:13:35 -0700
- To: whatwg/streams <streams@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 15 May 2017 23:14:10 UTC
Closes #446. --- Blocked on https://github.com/whatwg/dom/pull/437 finishing up, but it was important to write this up as a proof of concept; it shows that the AbortSignal design is good for our needs. There's a bit of a namespace collision in how streams has chosen writer.abort() to mean one thing which is a bit different from signal.abort() on a pipe. Maybe we should put a bit more about that in the developer-facing domintro boxes. But I don't think it's avoidable. /cc @annevk You can view, comment on, or merge this pull request online at: https://github.com/whatwg/streams/pull/744 -- Commit Summary -- * Allow aborting an ongoing pipe operation using AbortSignals -- File Changes -- M index.bs (24) -- Patch Links -- https://github.com/whatwg/streams/pull/744.patch https://github.com/whatwg/streams/pull/744.diff -- 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/pull/744
Received on Monday, 15 May 2017 23:14:10 UTC