Remove Socket token generic in favor of a struct #25
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Token has become a tuple struct wrapping a single uint. Using a generic
is not much use because supporting epoll and kqueue require that:
a) implement Copy
b) fit in the same number of bytes as uint
Given these requirements, it seems easier to just use a uint based
token.
Note that the TOKEN_{N} hack is to work around a rust bug (rust-lang/rust#17722) that has been fixed in a PR but is waiting to be pulled in.