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

@WebReflection 

I believe you do not hear me. I am not talking what there should be magic which cancels all potential async operations inside executor. This is approximately how it should be implemented for subclass:

```javascript
class AjaxPromise extends Promise {
  constructor(...) {
    var xhr = new XMLHttpRequest();
    // ...
    this[Symbol.lock] = () => {
       xhr.abort();
    }
  }
}

var ajax = function(config) {
  return new AjaxPromise(config);
};
```

> That plus the implicit exit behavior that does not fit with anything Promises, async, or await, related.

That is exactly what promises missing. So ```exit``` behavior does not fit, but ```cancellation``` behavior fits? I really do not see here much differences between these two concepts. ```async```/```await``` will form fine too.


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