Bump bytemuck from 1.18.0 to 1.19.0

[dependabot]

Bumps bytemuck from 1.18.0 to 1.19.0.

Changelog

Sourced from bytemuck's changelog.

bytemuck changelog

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.

1.16.2

• Fixes potential UB where BoxBytes could attempt to free a dangling pointer if the Layout is zero sized. This type was introduced in 1.14.1, so that version and the others up to and including 1.16.1 are now yanked for safety.

1.16.1

• NOT SEMVER SUPPORTED: Adds the nightly_float Cargo feature. This activates the f16 and f128 nightly features, and then provides Zeroable and Pod impls for those types.

1.16.0

• Adds a const_zeroed feature (MSRV 1.75) which puts a zeroed fn at the crate root. This is just like the Zeroable::zeroed method, but as a const fn.

1.15.0

This primarily relaxes the bounds on a From impl.

Previously:

... (truncated)

Commits

• 7b98ff1 chore: Release bytemuck version 1.19.0
• 422acc0 changelog.
• da9b187 add track_caller feature (#276)
• 1c09edf fix #274 (#275)
• 48952a0 chore: Release bytemuck_derive version 1.8.0
• 2cd9719 changelog
• a637e1d derive(Zeroable) on fieldful enums and repr(C) enums (#257)
• bb36879 Improve documentation of features. (#272)
• 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)

[dependabot]

Looks like bytemuck is up-to-date now, so this is no longer needed.