@poliorcetics Fair enough. What's the MSRV policy for windows-sys?

Current MSRV seems to be 1.48. This is the closest to a "policy" I find: microsoft/windows-rs#2300

windows-sys tries to not do releases (the rythm is ask-based, there will not be a release if no one asks for one, and there needs to be a reason), and same for the MSRV: unless needed (and given the crate is "just" bindings to the Windows API, it shouldn't often need it), windows-sys won't move much, if at all from what we saw in the last few months

EDIT: negative is hard

I can't get the GitHub Actions to let me run this in CI. Could you please rebase this on top of the latest main and push -f it to this branch? then I think I can run the CI and merge it.

Codecov Report

Merging #1595 (f493f89) into main (20ba41d) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1595   +/-   ##
=======================================
  Coverage   92.24%   92.24%           
=======================================
  Files         132      132           
  Lines       18845    18845           
  Branches      196      196           
=======================================
+ Hits        17383    17384    +1     
  Misses       1426     1426           
+ Partials       36       35    -1     

... and 1 file with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

Also of note: in the past the Windows-rs team has reduced the MSRV if it proved important for a crate and it was feasible: GuillaumeGomez/sysinfo#950 (comment) :)

Thanks!

Friends, I merged this but I am hoping to immediately replace it by PR #1542, which removes the windows-sys dependency. I would appreciate people taking a look at #1542 and testing it out on Aarch64 Windows systems.