I believe that the code in the execution context was originally there to use fork only if the current thread is the fork/join worker of the fork/join pool of that execution context -- only in this case we were doing the potentially more efficient `fork` -- otherwise we might get the task scheduled on the wrong pool

Since this is a method on the `ForkJoinTask` and not `ForkJoinPool`, I believe that is the reason there is no such check. Also, this method polls, it does not schedule for execution, so it might not be relevant which pool the polled task comes from.