Bump bytemuck from 1.14.0 to 1.14.3

[dependabot]

Bumps bytemuck from 1.14.0 to 1.14.3.

Changelog

Sourced from bytemuck's changelog.

1.14.3

• The new std simd nightly features are apparently arch-specific. This adjusts the feature activation to be x86/ x86_64 only.

1.14.2

• Changes the name of the Nightly feature activated by the crate's nightly_stdsimd feature. This is needed as of (approximately) Nightly 2024-02-06 and later, because the Nightly feature was changed.

1.14.1

• docs clarifications.

1.14

• write_zeroes and fill_zeroes functions: Writes (to one) or fills (a slice) zero bytes to all bytes covered by the provided reference. If your type has padding, this will even zero out the padding bytes.
• align_offset feature: causes pointer alignment checks to use the align_offset pointer method rather than as-casting the pointer to usize. This may improve codegen, if the compiler would have otherwise thought that the pointer address escaped. No formal benchmarks have been done either way.
• must_cast feature: Adds must_* family of functions. These functions will fail to compile if the cast requested can't be statically known to succeed. The error messages can be kinda bad when this happens, but eliminating the possibility of a runtime error might be worth it to you.

1.13.1

• Remove the requirement for the source data type to be AnyBitPattern on pod_collect_to_vec, allowing you to pod collect vecs of char into vecs of u32, or whatever.

1.13

• Now depends on bytemuck_derive-1.4.0
• Various small enhancements that would have been patch version updates, but which have been rolled into this minor version update.

1.12.4

• This has additional impls for existing traits and cleans up some internal code, but there's no new functions so I guess it counts as just a patch release.

1.12.3

• This bugfix makes the crate do stuff with Arc or not based on the target_has_atomic config. Previously, some targets that have allocation but

... (truncated)

Commits

• 49eed86 chore: Release bytemuck version 1.14.3
• 5f47176 clear up some warnings in tests.
• 031a035 ready changelog
• 1afddf9 Under features = ["nightly_stdsimd"], only enable stdarch_x86_avx512 feat...
• 04ed11b chore: Release bytemuck version 1.14.2
• d5f782b update changelog
• 678c923 Closes Lokathor/bytemuck#224, the Nightly feature n...
• 5f93477 Fix typo in AnyBitPattern docs (#221)
• 1e1a22e chore: Release bytemuck version 1.14.1
• 2ae1a14 changelog
• 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 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.