-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
time: Move DelayQueue to tokio-util #2897
Conversation
What part of the API was causing trouble? |
@Darksonn per @carllerche Tokio 1.0 won't initially expose DelayQueue as a stable API (see #2718), so this is moving it to tokio-util, which won't have the same stability guarantees. |
This change is intended to do the minimum to unblock 0.3; as such, for now, we duplicate the internal `time::wheel` structures in tokio-util, rather than trying to refactor things at this stage.
Force pushing to resolve conflicts. |
Not sure why the CI run was cancelled... Can someone please restart it? |
Done. |
Macos tests failed due to reaching unreachable code in the tokio scheduler... could this be an independent bug? @carllerche |
Failing line is https://github.com/tokio-rs/tokio/blob/master/tokio/tests/rt_common.rs#L569 Looks unrelated to the timer changes (but probably a legitimate bug) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, thanks 👍
This change is intended to do the minimum to unblock 0.3; as such, for now, we
duplicate the internal
time::wheel
structures in tokio-util, rather than tryingto refactor things at this stage.