Update Rust crate modular-bitfield to 0.13.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
modular-bitfield	dependencies	minor	0.11.2 → 0.13.0

---

Release Notes

modular-bitfield/modular-bitfield (modular-bitfield)

v0.13.1

Compare Source

Bug fixes

• #[repr] attributes containing lists like align(..) are now properly handled. Thanks, @​minty99! (#​132)

v0.13.0

Compare Source

Breaking changes

• The MSRV is now 1.76. This is not currently a hard requirement of modular-bitfield itself but is instead the path of least resistance due to changes to underlying dev-dependencies, so please open a ticket if you really need support for an even older version of Rust.
• From<[u8; {n}]> (when conversions are guaranteed) and TryFrom<[u8; {n}]> traits are now automatically derived by #[bitfield]. This will conflict with any manual implementations of the same trait, but you wrote those implementations to do this thing anyway, right? (#​120)
• The BitfieldSpecifier alias, which was deprecated in v0.12, is removed.

Enhancements

• Diagnostic messages around invalid bit counts have been improved.
• Minor documentation improvements for the Specifier trait.

Bug fixes

• Unnecessary brackets in the generated output which were triggering new Clippy lints in Rust 1.90+ have been fixed. (#​130)
• Unnecessary identity operations in the generated output which were triggering Clippy lints in some cases have been fixed. (#​131)

v0.12.0

Compare Source

Breaking changes

• The MSRV is now 1.70. This is not currently a hard requirement of modular-bitfield itself but is instead the path of least resistance due to changes to underlying dev-dependencies, so please open a ticket if you really need support for an even older version of Rust.
• The InvalidBitPattern::invalid_bytes field is now private. Use the InvalidBitPattern::invalid_bytes() method to access the invalid bytes (and InvalidBitPattern::new() to create new errors).

Deprecations

• To conform with idiomatic Rust code, the derive macro #[derive(BitfieldSpecifier)] has been renamed to #[derive(Specifier)] because it derives the Specifier trait. The deprecated alias will be removed in the next release of modular-bitfield.

Enhancements

• The syn dependency has been updated to version 2.
• Generated constructors and getters are now annotated with #[must_use]. (#​79)
• Structs with const generics can now use #[bitfield]. (#​87)

Bug fixes

• Enumeration variant names will no longer conflict with code generated by #[derive(Specifier)]. (#​82)
• Using #[bitfield] on an empty struct now emits an appropriate diagnostic instead of causing a compile-time arithmetic error. (#​104)
• Various fixes to lints. (#​62, #​66, #​93, #​95. Thanks, @​dimpolo, @​diseraluca, @​nilfit, and @​LDVSOFT!)
• Various fixes to documentation formatting. (#​91, #​101, #​103. Thanks, @​00xc, @​SebastianJL, and @​jruderman!)
• When automatically deriving Debug, tuple-like structs are now formatted normally instead of like structs with numeric fields.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

[sourcery-ai]

Reviewer's Guide

This pull request updates the modular-bitfield dependency from version 0.11.2 to 0.12.0 by modifying the version string in the Cargo.toml file.

Class Diagram for modular-bitfield InvalidBitPattern Update

classDiagram
    class InvalidBitPattern {
        <<struct>>
        -invalid_bytes: BytesType
        +new(...) InvalidBitPattern
        +invalid_bytes() BytesType
    }
    note for InvalidBitPattern "invalid_bytes field became private in v0.12.0.\nUse the invalid_bytes() method to access."

Loading

File-Level Changes

Change	Details	Files
Bump modular-bitfield dependency version.	Updated the modular-bitfield version string from 0.11.2 to 0.12.0.	memN0ps/eagle-rs/driver/Cargo.toml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.