Bump enumflags2 from 0.6.4 to 0.7.3

[dependabot]

Bumps enumflags2 from 0.6.4 to 0.7.3.

Release notes

Sourced from enumflags2's releases.

Release 0.7.3

• The code generated by the macro no longer triggers Clippy's use_self lint. To prevent further issues of this kind, Clippy now runs on the test suite in CI, with the pedantic and nursery lints enabled too.
• Some more functions are marked #[inline] now. This will probably improve downstream performance in non-LTO builds.
• Some more functions are marked #[must_use] now, at the suggestion of Clippy. If this triggers, your code was probably weird and/or broken, but it's not really a mistake I'd expect anyone to make.
• Minor documentation improvements.

Release 0.7.2

The iterator returned by BitFlags::iter now implements Clone.

Release 0.7.0

• Breaking change: instead of #[derive(BitFlags)], the macro is now #[bitflags]
  • This allows a long-awaited feature: when a discriminant isn't provided, the macro will choose an unused bit for you.
• You can now create instances of BitFlags without repeating the name: make_bitflags!(MyFlags::{Foo, Bar}) instead of MyFlags::Foo | MyFlags::Bar. Works in a const fn, too!
• Many new APIs that allow working with BitFlags in a const fn despite rustc limitations
• Many improved error messages
• Implementation details do not show up in user documentation anymore
• Breaking change: rename the RawBitFlags trait to BitFlag - there's nothing raw about it
• Breaking change: the not_literal feature doesn't exist, the relevant functionality is now enabled by default - there is no concern about confusing error messages anymore
• Breaking change: the #[repr(u??)] attribute is now required - previously, Rust's default of usize was used, which is a terrible idea for the size of a bitfield
• Breaking change: BitFlags::new is now called from_bits_unchecked - new suggests that this is the main, preferred way of creating BitFlags. This is not the case.
• the value returned by Default::default can now be customized with #[bitflags(default = Foo | Bar)]

Commits

• 624b1cf Release 0.7.3
• f66ee6c Actually, fuck the benchmark
• a4b96e4 Run clippy on the test suite
• 8d9e3ef Use Self whenever possible in generated code
• 8398e8e doc: "considered to be impossible" is not good phrasing
• 02bbb12 doc: link to the "Customizing Default" section on the Default impl
• 800234a Add some #[must_use] and #[inline] annotations.
• 872c555 Release 0.7.2
• 6b9b259 Specify the MSRV in Cargo.toml
• 923bede Mark the result of BitFlags::iter as Clone (#38)
• 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]

The following labels could not be found: A2-insubstantial, B0-silent, C1-low 📌.

[dependabot]

Superseded by #6.