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

O material afetado é o artigo “isMounted is an Antipattern” vinculado na issue; comece revisando seu exemplo de makeCancelable e a discussão referenciada. Atualize a documentação para que suas orientações sobre vazamentos de memória estejam tecnicamente corretas e, em seguida, verifique se o artigo não recomenda mais a implementação contestada.