-
Notifications
You must be signed in to change notification settings - Fork 531
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
Update the current Scheduler api? #3356
Comments
That's correct. Unfortunately, we cannot change the API at this point due to compatibility constraints.
It can, and it will very soon! See this PR: |
And then, a user can using a HashWheelTimer which turn out the timeout as an event and send to the workerThread's taskQueue. Update: |
@armanbilge May I have a question about when or what conditions are satisfied, then we could make improvements and break compatibility constraints. Thanks! |
When we are working on Cats Effect 4, which would be a major, breaking change. But there are no concrete plans for this at the moment. It would probably happen around the same time as Cats 3, which is also rather hypothetical. |
Hi I am still new on cats-effect ,but I think the current api of Scheduler can be updated with :
And seems like the only way to cancel the current scheduled task is by call the returning
Runnable
with the current Scheduler api?As I'm starting using vertx these days, and I think the
cats.effect.unsafe.WorkerThread
can do the scheduling too, just as Netty's Eventloop does, which employed an PriorityQueue to do that.The text was updated successfully, but these errors were encountered: