I have a use case where the exact timing of a task is not that important, but where I already have a main loop that could do manual polling on the scheduler. The fact that the closure with the task needs to be Send adds quite some boilerplate though (Arc<Mutex<...>> and all the corresponding locking code).
As far as I've seen, the CoreExecutor is based on wakeup timers, right? How hard would it be to add a LocalExecutor with the same scheduling concept as the CoreExecutor, but where the user has to manually poll / query the executor in regular intervals?
I have a use case where the exact timing of a task is not that important, but where I already have a main loop that could do manual polling on the scheduler. The fact that the closure with the task needs to be
Sendadds quite some boilerplate though (Arc<Mutex<...>>and all the corresponding locking code).As far as I've seen, the
CoreExecutoris based on wakeup timers, right? How hard would it be to add aLocalExecutorwith the same scheduling concept as theCoreExecutor, but where the user has to manually poll / query the executor in regular intervals?