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
Use task pool instead of handwritten implementation #6
Conversation
This code does not compile for me:
|
Can you check
|
It works! And it's a bit faster, too. |
Great. I'm happy that all the boilerplate is now gone. |
Cool that the task interface fits the problems here! I'm wondering if it would make sense to make the pool of size |
The main domain does participate in working on tasks. For example, you can create a pool with |
Ah cool |
Just had a look at |
Ah sorry - it's |
Yeah. The idea is to set up the pool (which essentially sets up a shared channel as a work-stealing queue). The worker domains first wait on the channel for tasks and execute them when one is available. And as you've observed, |
No description provided.