-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cargo: Bump windows
crate range to 0.53-0.56
#213
Conversation
0.54
crate0.56
crate
The I'm not sure why it's not mentioned in the release notes. |
aa99351
to
f414708
Compare
0.56
cratewindows
crate range to 0.53-0.56
This would be great to get in, I've started depending on it locally. Is there anything an outsider could do to help move this along? |
f414708
to
4a21252
Compare
4a21252
to
2e86544
Compare
Because of the refactoring of `CanInto` (to now only support `unsafe` `IntoParam` boilerplate for `Abi` purposes) in favour of regular `From` implementations for type-safe upcasting, the new releases are no longer backwards-compatible with `windows 0.51-0.52`.
Most namespaces are parents which are enabled automatically when enabling their childeren (and the root `Win32` namespace depends on `Win32_Foundation` since newer `windows` releases). Except `Direct3D`, which is not required for `gpu-allocator` but only used in the examples.
2e86544
to
e52803d
Compare
windows
crate range to 0.53-0.56
windows
crate range to 0.53-0.57
Looks like |
e52803d
to
9fc33b3
Compare
windows
crate range to 0.53-0.57
windows
crate range to 0.53-0.56
Ugh, the merge-commit title failed to update. |
Allow
windows 0.53
all the way up to and including0.57
to be used, and remove some unused features from the core crate.