HQSquantumsimulations / qoqo-quest

Other
7 stars 8 forks source link

Bump bytemuck from 1.13.0 to 1.13.1 #149

Open dependabot[bot] opened 1 year ago

dependabot[bot] commented 1 year ago

Bumps bytemuck from 1.13.0 to 1.13.1.

Changelog

Sourced from bytemuck's changelog.

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 not atomics were getting errors. This raises the MSRV of the extern_crate_alloc feature to 1.60, but opt-in features are not considered to be hard locked to 1.34 like the basic build of the crate is.

1.12.2

  • Fixes try_pod_read_unaligned bug that made it always fail unless the target type was exactly pointer sized in which case UB could happen. The CheckedBitPattern::is_valid_bit_pattern was being asked to check that a reference to the pod value was a valid bit pattern, rather than the actual bit pattern itself, and so the check could in some cases be illegally bypassed.

1.12.1

  • Patch bumped the required bytemuck_derive version because of a regression in how it handled align(N) attributes.

1.12

  • This minor version bump is caused by a version bump in our bytemuck_derive dependency, which is in turn caused by a mixup in the minimum version of syn that bytemuck_derive uses. See Issue 122. There's not any specific "new" API as you might normally expect from a minor version bump.
  • pali fixed a problem with SPIR-V builds being broken. The error handling functions were trying to be generic over Display, which the error types normally support, except on SPIR-V targets (which run on the GPU and don't have text formatting).

... (truncated)

Commits


Dependabot compatibility score

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