fix(deps): update rust crate bitflags to 2.5.0 - autoclosed #84
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 PR contains the following updates:
2
->2.5.0
Release Notes
bitflags/bitflags (bitflags)
v2.5.0
Compare Source
What's Changed
Debug
forFlag<B>
by @tgross35 in https://github.com/bitflags/bitflags/pull/398New Contributors
Full Changelog: bitflags/bitflags@2.4.2...2.5.0
v2.4.2
Compare Source
What's Changed
unused_tuple_struct_fields
lint by @dtolnay in https://github.com/bitflags/bitflags/pull/393local_inner_macros
by @dtolnay in https://github.com/bitflags/bitflags/pull/392New Contributors
Full Changelog: bitflags/bitflags@2.4.1...2.4.2
v2.4.1
Compare Source
What's Changed
Full Changelog: bitflags/bitflags@2.4.0...2.4.1
v2.4.0
Compare Source
What's Changed
New Contributors
Full Changelog: bitflags/bitflags@2.3.3...2.4.0
v2.3.3
Compare Source
Changes to
-=
The
-=
operator was incorrectly changed to truncate bits that didn't correspond to valid flags in2.3.0
. This hasbeen fixed up so it once again behaves the same as
-
anddifference
.Changes to
!
The
!
operator previously calledSelf::from_bits_truncate
, which would truncate any bits that only partiallyoverlapped with a valid flag. It will now use
bits & Self::all().bits()
, so any bits that overlap any bitsspecified by any flag will be respected. This is unlikely to have any practical implications, but enables defining
a flag like
const ALL = !0
as a way to signal that any bit pattern is a known set of flags.Changes to formatting
Zero-valued flags will never be printed. You'll either get
0x0
for empty flags using debug formatting, or theset of flags with zero-valued flags omitted for others.
Composite flags will no longer be redundantly printed if there are extra bits to print at the end that don't correspond
to a valid flag.
What's Changed
Full Changelog: bitflags/bitflags@2.3.2...2.3.3
v2.3.2
Compare Source
What's Changed
New Contributors
Full Changelog: bitflags/bitflags@2.3.1...2.3.2
v2.3.1
Compare Source
What's Changed
Full Changelog: bitflags/bitflags@2.3.0...2.3.1
v2.3.0
Compare Source
Major changes
BitFlags
trait deprecated in favor ofFlags
traitThis release introduces the
Flags
trait and deprecates theBitFlags
trait. These two traits are semver compatible so if you have public API code depending onBitFlags
you can move toFlags
without breaking end-users. This is possible because theBitFlags
trait was never publicly implementable, so it now carriesFlags
as a supertrait. All implementations ofFlags
additionally implementBitFlags
.The
Flags
trait is a publicly implementable version of the oldBitFlags
trait. The originalBitFlags
trait carried some macro baggage that made it difficult to implement, so a newFlags
trait has been introduced as the One True Trait for interacting with flags types generically. See the themacro_free
andcustom_derive
examples for more details.Bits
trait publicly exposedThe
Bits
trait for the underlying storage of flags values is also now publicly implementable. This lets you define your own exotic backing storage for flags. See thecustom_bits_type
example for more details.What's Changed
Full Changelog: bitflags/bitflags@2.2.1...2.3.0
v2.2.1
Compare Source
What's Changed
Full Changelog: bitflags/bitflags@2.2.0...2.2.1
v2.2.0
Compare Source
What's Changed
New Contributors
Full Changelog: bitflags/bitflags@2.1.0...2.2.0
v2.1.0
Compare Source
What's Changed
New Contributors
Full Changelog: bitflags/bitflags@2.0.2...2.1.0
v2.0.2
Compare Source
What's Changed
Full Changelog: bitflags/bitflags@2.0.1...2.0.2
v2.0.1
Compare Source
What's Changed
New Contributors
Full Changelog: bitflags/bitflags@2.0.0...2.0.1
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.