Re: [fetch] Aborting a fetch (#27)

@benjamingr I'm glad you've arrived at the same conclusion I have that what you call abort semantics just wont work with promises. My concern with the more benign ignore semantics you mention is that it I see little technical difference - the lack of a way to consume one of these promises without implicit interest is still a problem -  I see merely a recasting of expectations, with little guidance for folks looking for the cancellation hammer.

You make a distinction between single and multiple subscriber promise-use as if they're two ways of working that users can choose between. But users compose promise-chains from calls to functions from all over the place that they don't control, and so they cannot guarantee that the net promise-chain is free of multiple subscribers (now or in future version of libraries), as I mention in https://github.com/whatwg/fetch/issues/27#issuecomment-102500578. Users also shouldn't have to care about how functions are implemented in this regard, so such an expectation breaks an important abstraction.

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/27#issuecomment-176414285