Currently, the runInLoop callback is executed forever, which is not nice, because some use cases require us to loop a certain function forever until some condition happens. It makes sense for the callback to signal this. I guess the response could be shouldContinueRunning, e.g. returning false from the callback will stop the loop.
Currently, the
runInLoopcallback is executed forever, which is not nice, because some use cases require us to loop a certain function forever until some condition happens. It makes sense for the callback to signal this. I guess the response could beshouldContinueRunning, e.g. returning false from the callback will stop the loop.