-
Notifications
You must be signed in to change notification settings - Fork 280
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
Test out Service::disarm for all tower services #434
base: master
Are you sure you want to change the base?
Conversation
|
||
// Take self.ready so we can call &mut self methods below | ||
let mut ready = std::mem::take(&mut self.ready); | ||
for (key, (mut svc, cancel)) in ready.drain(..) { |
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.
ouch :(
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.
Yeah... It's not expensive (like, it won't allocate for example), but it does mean that you might un-ready a bunch of services.
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 fine overall, I am just cautious about the panic for calling disarm wrong over just making it best effort?
I'd like @seanmonstar, @hawkw and @carllerche to take a look here too.
See #408 and rust-lang/futures-rs#2109.