Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non-Send tasks #3

Open
dbrgn opened this issue Oct 15, 2017 · 0 comments
Open

Non-Send tasks #3

dbrgn opened this issue Oct 15, 2017 · 0 comments

Comments

@dbrgn
Copy link

dbrgn commented Oct 15, 2017

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant