Bump bitflags to 2.3.2 #426
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Seems like the bitflags changes are semver breaking and this would require a bump to |
|
Thanks for the PR!
Would it be possible to implement a custom |
Freax13
approved these changes
Jun 17, 2023
There was a problem hiding this comment.
This looks good to me! According to the release notes for bitflags 2.0.0 these are all the changes required to maintain backwards compatibility.
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
All of the types that use
bitflags!have#[derive(PartialEq, Eq, PartialOrd, Ord, Hash, Debug, Clone, Copy)]on them to preserve backwards compatability as recommended by the bitflags changelog.