Move isWaitForAll_ from ThreadPoolExecutor to IOThreadPoolExecutor
Summary: I randomly ran into this while working on something else: ThreadPoolExecutor has a field `isWaitForAll_` which: * is only used in its subclass, `IOThreadPoolExecutor` * has a comment referencing evbs, which ThreadPoolExecutor doesn't have relationship to but the subclass does. Looks like this is an artefact of some old refactoring Reviewed By: yfeldblum Differential Revision: D31117228 fbshipit-source-id: ea7d1753a0d75ab8911cec68f3b6fb8c1f07c569
Showing
Please register or sign in to comment