You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was updating mio to use windows-sys instead of winapi as windows-sys covers most of Windows API surface and most importantly is maintained and updated frequently as opposed to winapi, but this crate still provides types and functions not available in the windows-sys crate which is to be expected, however since it relies on winapi internally we'll be pulling in 2 versions of windows bindings, and in some cases need to transmute between the "same" type, so just wanted to open this issue to begin a discussion about whether this is something that would be acceptable to this project.
The text was updated successfully, but these errors were encountered:
I was updating
mio
to usewindows-sys
instead ofwinapi
aswindows-sys
covers most of Windows API surface and most importantly is maintained and updated frequently as opposed towinapi
, but this crate still provides types and functions not available in thewindows-sys
crate which is to be expected, however since it relies onwinapi
internally we'll be pulling in 2 versions of windows bindings, and in some cases need to transmute between the "same" type, so just wanted to open this issue to begin a discussion about whether this is something that would be acceptable to this project.The text was updated successfully, but these errors were encountered: