You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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 aLocalExecutor
with the same scheduling concept as theCoreExecutor
, but where the user has to manually poll / query the executor in regular intervals?The text was updated successfully, but these errors were encountered: