Re: [whatwg/dom] Adding a return value to `controller.abort()` which represents abort completion (#881)

OK, at the risk of forking the thread and losing the fairly nice design work we've been doing so far, here's an alternate solution that involves a lot less moving parts:

```js
const controller = new AbortController();
const pipePromise = readable1.pipeTo(writable, { preventAbort: true, signal: controller.signal });

// ... some time later ...
controller.abort();
await DOMException.ignoreAborts(pipePromise);

// Start the new pipe!
readable2.pipeTo(writable);
```

It's a little rough (e.g., slightly more to type; not a huge fan of the name `ignoreAborts` but I want it to be short; it's a bit strange that a function with a generic name like "ignoreAborts" specifically operates on promise arguments...). But it's probably a cleaner separation of concerns, whereas my original suggestion mixes things up a decent bit in the name of convenience.

-- 
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/dom/issues/881#issuecomment-675003948