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.
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