Update to bitflags 2.1.0 #952
Closed
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
rcook
force-pushed
the
rcook-bitflags-2.1.0
branch
from
6532a79
to
c16cb35
Compare
rcook
force-pushed
the
rcook-bitflags-2.1.0
branch
from
c16cb35
to
d519d14
Compare
edrevo
approved these changes
Jul 7, 2023
|
Closing as merged via #973. I ran into a problem since the source repo was archived. |
auto-merge was automatically disabled
July 28, 2023 18:37
Pull request was closed
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.
This upgrades this project to use bitflags 2.1.0 which includes some ergonomic improvements for working with bit flags including iterators over name and values of the bit flag members. Change derives Debug and PartialEq for types so that we can display values for debugging and compare them.