Upgrade bitflags to 2.4.1 #241
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
GnomedDev
force-pushed
the
upgrade-bitflags
branch
from
bf1a334
to
102384b
Compare
GnomedDev
force-pushed
the
upgrade-bitflags
branch
from
102384b
to
98740a5
Compare
|
Thanks for doing this. Unfortunately, I already inadvertently did this while working on the |
|
No problem |
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 is a breaking change, so should be tagged with 0.6.
Replaces the outdated bitflags 1.2.1 with 2.4.1, which reduces downstream duplicate dependencies and allows removing the ChannelsIter as this is automatically added by the bitflags macro.