Repository navigation
Replace winapi with windows-sys? #9
Description
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.
Activity
Skgland commentedon Mar 27, 2026
Why was this closed as completed?
Jake-Shadle commentedon Mar 27, 2026
I was pruning issues I'd opened that hadn't gotten any response or that I don't care about any longer.
Skgland commentedon Mar 27, 2026
Wouldn't closing as not planned be more appropriate then? (Maybe with a small comment)
Would a PR doing the change still be appreciated?
Jake-Shadle commentedon Mar 27, 2026
It's not my repo, #17 already exists.
Skgland commentedon Mar 27, 2026
Ah, I overlooked that. A bit unfortunate that issue authors can't choose a different close reason.
Yeah, I saw that that PR exists, but it has merge conflicts and hasn't been updated in three years.
Skgland commentedon Mar 28, 2026
Ah, I don't think the PR actually has blocking merge conflicts, GitHub UI is just contradicting itself.
Can it be cleanly merged or are there conflicts that must be resolved!?