It was not as simple as modifying the usize to u64 because mio uses an usize internally too and the value is clamped by the 32-bits OS poll.
The fix encodes the adapter id and resource type information into the less significant bits instead of the most significant bits to be sure that whatever word size is used in the OS, these values are always encoded into the ResourceId.
From: https://github.com/lemunozm/message-io/issues/41
It was not as simple as modifying the
usizeto u64 becausemiouses anusizeinternally too and the value is clamped by the 32-bits OS poll.The fix encodes the adapter id and resource type information into the less significant bits instead of the most significant bits to be sure that whatever word size is used in the OS, these values are always encoded into the
ResourceId.