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

The .next was compared to .cancel as method you invoke outside. Calling
cancel on an async function means implicitly invoke cancel to the
cancelable promise hold in await. About constructing cancelable promise is
not your concern. Fetch will do what it has to do, you are not responsible
for that, the API internally knows how to cancel. If you want to make a
promise cancelable you do that, of you don't want a cancelable promise you
don't. Better?
On Mar 30, 2015 8:01 PM, "Kyle Simpson" <notifications@github.com> wrote:

> you externally invoke .next(value) there
>
> Where do you invoke this? On the return value from an async function?
> That's currently thought of as being a normal promise, not an iterator, so
> next(..) call there wouldn't make any sense.
>
> It's also not clear how that addresses what you're talking about, or
> answering my direct question: *In your view of cancelable promises as
> being decided based on what you pass into the promise constructor, how do
> you do that when the promise is constructed implicitly behind the scenes?*
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/whatwg/fetch/issues/27#issuecomment-87774559>.
>


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