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

@WebReflection 

> > Introducing this change directly to Promise feels a bit dangerous.
> 
> ... again, how is that since nobody cancels Promises these days ? Where is the dangerous part? If that returns suddenly a cancelable Promise, what would change?

Setting `fetch(..)` aside entirely, if ES7 `Promise` instances all of a sudden got a `cancel()` method on them, an existing system written in ES6 which *relies* on separate consumers of `p1` and `p2` ***not being able to interfere*** with each other (by virtue of there being no such `cancel()` on promise instances) could/would break if the consumer of the `p1` promise could all of a sudden start interfering with the consumer of the `p2` promise by calling `p1.cancel(..)`.

This is precisely the "action at a distance" concern I've talked about at length earlier in this thread.

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