-
Notifications
You must be signed in to change notification settings - Fork 32
Switch from winapi to windows-rs #71
Comments
The API itself hasn't been updated even longer. We target APIs from a lot of years ago. When I've previously looked at the It does look like an eventuality of switching to Is there any benefit in specific why you would like to switch sooner or is it because |
Using the
Sure there is no immediate need, but it feels silly writing more code with winapi when it will have to be changed eventually. |
I can understand that. However I would like to point out that the |
Might be worth pointing out that some configs already build |
I've been peeking at this off and on and at this point have some amount of code converted, currently as a big ball of changes and not trying to do something piece by piece (which seems hard). I can't compare build times until it is done, but so far, there's some nice reduction in code in parts of the Glazier code (and like I said before, when I'm saying this here so that 1) interested parties know and 2) interested parties don't start trying to do the same thing yet and duplicate any effort. I'd started as I was looking at using some other APIs and found that they were exposed via |
FWIW, now that I'm a couple of hours in, I'm probably going to toss it and switch to |
The winapi crate hasn't been updated in over a year and has been deprecated by windows-rs which are the official rust bindings to the windows api.
I think it would be better to switch sooner rather than later.
One consideration would be whether to use the
windows
orwindows-sys
crate.The text was updated successfully, but these errors were encountered: