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

> Consuming a promise is very explicit interest in its result.

@benjamingr that's certainly not always the case, e.g. when result is `undefined` for one. There's also lots of time-math, scheduling and utility functions one can do and make that build on promises without taking a direct interest in their result (e.g. `Promise.all` or the `queue(() => {})` thing I reference in https://github.com/whatwg/fetch/issues/27#issuecomment-102500578 which is from [real code I wrote](http://mxr.mozilla.org/mozilla-central/source/dom/media/PeerConnection.js?rev=d2c568567473#488)) . But you didn't address my concern that there's no way for a user to ensure this behavior in other libraries, which makes this action-at-a-distance of the worst kind in my book: Users and library authors shouldn't have to worry about indirectly affecting client code like this.

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