Incorrect documentation for fixing memory leaks

The "isMounted is an Antipattern" documentation article suggest avoiding memory leaks with makeCancelable, but this doesn't actually solve the issue since the callback is still referenced. The garbage collector does not understand that setting hasCanceled_ means that resolve will never be called, so it cannot release resolve or the references contained within. Even if it could, reject might also reference this, so memory leaks could still exist. Instead, makeCancelable should store the resolve and reject callbacks itself, and it should null them out on cancelation.

Another user pointed this issue out in https://github.com/facebook/react/issues/5465#issuecomment-287113777

Il materiale interessato è l’articolo “isMounted is an Antipattern” collegato nell’issue; inizia esaminando il suo esempio di makeCancelable e la discussione a cui fa riferimento. Aggiorna la documentazione in modo che le indicazioni sulle perdite di memoria siano tecnicamente corrette, quindi verifica che l’articolo non raccomandi più l’implementazione contestata.