Skip to content

Conversation

@ColinBradley
Copy link
Contributor

Hope this is okay!
closes #1031

@ColinBradley
Copy link
Contributor Author

Actually, I've just noticed that this is a very minor breaking change, as previous method groups that are passed in could have an overload that took in a cancellation token, so it becomes ambiguous with the new overload on SimpleRetryHandler. It'd be a silly situation to get into, but Task.Delay is just one such example! That's why the code uses a named parameter to get around the ambiguity.

Booo C#!

So, I guess it's either: allow the minor breaking change or don't overload the constructor and instead set the sleeper with a method or something? But that seems a bit mad?

@JohnnyCrazy
Copy link
Owner

Hi,

Thanks for that, looks like a good change to have!

Could you rebase your changes on the latest master so we can get the CI to pass? LGTM then!

@ColinBradley
Copy link
Contributor Author

Cool! All done.

@JohnnyCrazy JohnnyCrazy merged commit 8293f64 into JohnnyCrazy:master Mar 31, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

SimpleRetryHandler doesn't use the CancellationToken when sleeping

2 participants