build(deps): update bitflags requirement from 1.2.1 to 2.3.3

[dependabot]

Updates the requirements on bitflags to permit the latest version.

Release notes

Sourced from bitflags's releases.

2.3.3

Changes to -=

The -= operator was incorrectly changed to truncate bits that didn't correspond to valid flags in 2.3.0. This has been fixed up so it once again behaves the same as - and difference.

Changes to !

The ! operator previously called Self::from_bits_truncate, which would truncate any bits that only partially overlapped with a valid flag. It will now use bits & Self::all().bits(), so any bits that overlap any bits specified 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 the set 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

• Fix up incorrect sub assign behavior and other cleanups by @​KodrAus in bitflags/bitflags#366

Full Changelog: bitflags/bitflags@2.3.2...2.3.3

Changelog

Sourced from bitflags's changelog.

2.3.3

Changes to -=

The -= operator was incorrectly changed to truncate bits that didn't correspond to valid flags in 2.3.0. This has been fixed up so it once again behaves the same as - and difference.

Changes to !

The ! operator previously called Self::from_bits_truncate, which would truncate any bits that only partially overlapped with a valid flag. It will now use bits & Self::all().bits(), so any bits that overlap any bits specified 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 the set 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

• Fix up incorrect sub assign behavior and other cleanups by @​KodrAus in bitflags/bitflags#366

Full Changelog: bitflags/bitflags@2.3.2...2.3.3

2.3.2

What's Changed

• [doc] [src/lib.rs] delete redundant path prefix by @​OccupyMars2025 in bitflags/bitflags#361

New Contributors

• @​OccupyMars2025 made their first contribution in bitflags/bitflags#361

Full Changelog: bitflags/bitflags@2.3.1...2.3.2

2.3.1

What's Changed

• Fix Self in flags value expressions by @​KodrAus in bitflags/bitflags#355

Full Changelog: bitflags/bitflags@2.3.0...2.3.1

2.3.0

What's Changed

• Support ejecting flags types from the bitflags macro by @​KodrAus in bitflags/bitflags#351

Full Changelog: bitflags/bitflags@2.2.1...2.3.0

... (truncated)

Commits

• 6ed2e8d Merge pull request #367 from KodrAus/cargo/2.3.3
• 290961e prepare for 2.3.3 release
• 3ac85e2 Merge pull request #366 from KodrAus/feat/test-cleanups
• 64b7c98 include tests for hex, binary, and octal
• b344782 remove unneeded condition
• 8f5f7cc fill in tests for intersection and union
• 481e13f fill in tests for insert remove and toggle
• 4b71f86 only yield flags if they include as-yet unyielded bits
• 330a028 fill in some more tests
• b933056 fill in tests for from_* methods
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #191.