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

Registration should explicitly deregister the io on drop. #168

Closed
carllerche opened this issue Mar 2, 2018 · 0 comments
Closed

Registration should explicitly deregister the io on drop. #168

carllerche opened this issue Mar 2, 2018 · 0 comments

Comments

@carllerche
Copy link
Member

No description provided.

@carllerche carllerche added this to the v0.1.1 - Tokio Runtime milestone Mar 6, 2018
carllerche added a commit that referenced this issue Mar 6, 2018
Mio will be requiring `deregister` to be called explicitly in order to
guarantee that Poll releases any state associated with the I/O resource.
See tokio-rs/mio#753.

This patch adds an explicit `deregister` function to `Registration` and
updates `PollEvented` to call this function on drop.

`Registration::deregister` is also called on `PollEvented::into_inner`.

Closes #168
carllerche added a commit that referenced this issue Mar 6, 2018
Mio will be requiring `deregister` to be called explicitly in order to
guarantee that Poll releases any state associated with the I/O resource.
See tokio-rs/mio#753.

This patch adds an explicit `deregister` function to `Registration` and
updates `PollEvented` to call this function on drop.

`Registration::deregister` is also called on `PollEvented::into_inner`.

Closes #168
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

No branches or pull requests

1 participant