- From: Martin Thomson <notifications@github.com>
- Date: Fri, 27 Mar 2015 18:34:37 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
Received on Saturday, 28 March 2015 01:34:59 UTC
@jyasskin I agree regarding the two vs. three state thing. I don't see people handling cancellation unless it causes rejection. I can see where @jakearchibald is coming from there, with the cancellation avoiding `.catch()` handlers all down the chain, but I don't see that as materially different from defining a `reallyReject` and matching `.reallyCatch()` functions. I acknowledge the bug in my example - it's been a very long IETF week - but will stick to my thesis here. This is a footgun. q: What happens to a `CancellablePromise` when the anchor promise (the one that can actually be cancelled, not its dependents) resolves? Does the `.abort()` function on it just fail with a `TooLateError`? --- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/27#issuecomment-87138377
Received on Saturday, 28 March 2015 01:34:59 UTC