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

Mutable state is perfectly okay, as long as the mutation is not observable. If a task is canceled once all consumers stop awaiting its result, it's like a tree falling in the forest when no one is around to hear it. If I can cancel your promise, that's mutation that you can observe. That's a recipe for disaster.

I understand your frustration Andrea. Everybody wants standards to be well-thought out the first time around. It does seem like we are sort of agreeing though. Ideally fetch would not exist, and if it truly does not meet the needs of developers, it will eventually fade away. Out of all the options we have, I think an easy-to-use drop in replacement library is the best one. 

JH

> On Apr 3, 2015, at 5:13 PM, Andrea Giammarchi <notifications@github.com> wrote:
> 
> Also last thought on this: by specifications, the User Agent is capable of dropping the request internally triggering a Fatal error so all this immutable Promise is a lie because it's just virtually effective in User Land but in core the state is mutable because that's needed
> 
> So how do we move on here, since deprecating fetch thread has been closed, and Tasks are not even close to be a specification standard?
> 
> —
> Reply to this email directly or view it on GitHub.
> 


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