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

Remove error case from the infallible DelayQueue::poll_elapsed #4241

Merged
merged 4 commits into from
Feb 9, 2022

Conversation

Ralith
Copy link
Contributor

@Ralith Ralith commented Nov 18, 2021

Motivation

It is unclear why DelayQueue::poll_elapsed might fail, and therefore how a caller should respond to a failure.

Solution

As the method cannot, in fact, fail, removing the possibility of returning an error avoids confusion for callers.

@Ralith Ralith force-pushed the infallible-poll-elapsed branch 2 times, most recently from ce53a53 to 675c262 Compare November 18, 2021 05:12
@Darksonn Darksonn added A-tokio-util Area: The tokio-util crate M-time Module: tokio/time labels Nov 18, 2021
@Darksonn
Copy link
Contributor

This is a breaking change, but we also have two other pending changes that are breaking, so it might be time to do a breaking tokio-util release soon.

@tobz tobz added the S-breaking-change A breaking change that requires manual coordination to be released. label Dec 6, 2021
@tobz
Copy link
Member

tobz commented Feb 8, 2022

Making sure the CI passes after resolving the merge conflict before actually merging.

@tobz tobz merged commit cf38ba6 into tokio-rs:master Feb 9, 2022
@Ralith Ralith deleted the infallible-poll-elapsed branch February 9, 2022 03:05
@Ralith
Copy link
Contributor Author

Ralith commented Feb 9, 2022

Thanks for sorting out the conflicts!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-tokio-util Area: The tokio-util crate M-time Module: tokio/time S-breaking-change A breaking change that requires manual coordination to be released.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants