Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447)

@getify 

The entire reason we all like the controller approach so much is that it lets TC39 hash out cancellation (as a concept) in the language and decide on how APIs with cancellation should look like while providing a way to abort a fetch which is future compatible to API changes with cancellation.

It provides a simple extensible solution for a problem developers have with the current API.

The meeting consensus wasn't against or for different methods or subclassing promises (we were actually mostly against that) or `.cancel` or destructuring. It was to decide on a simple extensible API (controller) and consider adding these other things later - depending on how/if people wrap `.fetch` and how the language settles cancellation in the future.

-- 
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/fetch/issues/447#issuecomment-275120594