Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update rust crate bitflags to 2.5.0 - autoclosed #84

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 1, 2024

Mend Renovate

This PR contains the following updates:

Package Type Update Change
bitflags dependencies minor 2 -> 2.5.0

Release Notes

bitflags/bitflags (bitflags)

v2.5.0

Compare Source

What's Changed

New Contributors

Full Changelog: bitflags/bitflags@2.4.2...2.5.0

v2.4.2

Compare Source

What's Changed

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

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 of Flags trait

This release introduces the Flags trait and deprecates the BitFlags trait. These two traits are semver compatible so if you have public API code depending on BitFlags you can move to Flags without breaking end-users. This is possible because the BitFlags trait was never publicly implementable, so it now carries Flags as a supertrait. All implementations of Flags additionally implement BitFlags.

The Flags trait is a publicly implementable version of the old BitFlags trait. The original BitFlags trait carried some macro baggage that made it difficult to implement, so a new Flags trait has been introduced as the One True Trait for interacting with flags types generically. See the the macro_free and custom_derive examples for more details.

Bits trait publicly exposed

The 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 the custom_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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot changed the title fix(deps): update rust crate bitflags to 2.5.0 fix(deps): update rust crate bitflags to 2.5.0 - autoclosed May 5, 2024
@renovate renovate bot closed this May 5, 2024
@renovate renovate bot deleted the renovate/bitflags-2.x branch May 5, 2024 09:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants