-
-
Notifications
You must be signed in to change notification settings - Fork 175
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better waitAll on scheduler #4486
Labels
Comments
Might be cool to have it before the next major, see #3891 |
Wait might not be the best name actually. Maybe we should have called it something like: run, release, unlock... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
馃挕 Idea
While waitAll is not the best option as it tend not to be explicit on what the user want (mostly regarding the speed of scheduling), it's still the simplest option in many case.
We should make it able to wait less strictly. While playing around with it, it appears that the simplest option is probably to wrap calls with custom acts either
Well, these options might be directly offered on the scheduler at creation time.
The text was updated successfully, but these errors were encountered: