build(deps): bump bytemuck_derive from 1.8.1 to 1.9.3

[dependabot]

Bumps bytemuck_derive from 1.8.1 to 1.9.3.

Changelog

Sourced from bytemuck_derive's changelog.

bytemuck changelog

1.22

• Add the pod_saturating feature, which adds Pod impls for Saturating<T> when T is already Pod.
• A bump in the minimum bytemuck_derive dependency from 1.4.0 to 1.4.1 to avoid a bug if you have a truly ancient cargo.lock file sitting around.
• Adds Send and Sync impls to BoxBytes.

1.21

• Implement Pod and Zeroable for core::arch::{x86, x86_64}::__m512, __m512d and __m512i without nightly. Requires Rust 1.72, and is gated through the avx512_simd cargo feature.
• Allow the use of must_cast_mut and must_cast_slice_mut in const contexts. Requires Rust 1.83, and is gated through the must_cast_extra cargo feature.
• internal: introduced the maybe_const_fn macro that allows defining some function to be const depending upon some cfg predicate.

1.20

• New functions to allocate zeroed Arc and Rc. Requires Rust 1.82
• TransparentWrapper impls for core::cmp::Reverse and core::num::Saturating.
• internal: Simplified the library's fill_zeroes calls to write_bytes

1.19

• Adds the #[track_caller] attribute to functions which may panic.

1.18

• Adds the latest_stable_rust cargo feature, which is a blanket feature that turns all other features on that are both sound and compatible with Stable rust.

1.17.1

• Adds #[repr(C)] to the union Transmute<A, B> type that's used internally for most of the transmutations.

1.17.0

• Makes the must_cast versions of the by-value and by-ref casts be const. The mut ref cast is unaffected for now (mut references aren't yet stable in const fn). This increases the MSRV of using that particular feature from 1.57 to 1.64.

1.16.3

• Fully described in Lokathor/bytemuck#256, This makes casting slices to/from ZST elements more consistent between the crate's core module and other modules.

... (truncated)

Commits

• See full diff 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)