Deprecate Future::onError
Summary: onError is to be phased out because: * It is weakly typed * (most seriously) It loses the executor and so terminates a via chain silently causing subsequent work to run in the wrong place onError is replaced with thenError which fixes both problems. This diff merely deprecates it to allow for a gentle phase out. Reviewed By: yfeldblum Differential Revision: D13418290 fbshipit-source-id: a0c5e65a97ed41de18d85ceab258417355a43139
Showing
Please register or sign in to comment