GlareDB / glaredb_next

5 stars 1 forks source link

chore(deps): bump twox-hash from 1.6.3 to 2.0.1 #327

Closed dependabot[bot] closed 2 weeks ago

dependabot[bot] commented 2 weeks ago

Bumps twox-hash from 1.6.3 to 2.0.1.

Changelog

Sourced from twox-hash's changelog.

2.0.1 - 2024-11-04

Fixed

  • Removed a panic that could occur when using XxHash3_64 to hash 1 to 3 bytes of data in debug mode. Release mode and different lengths of data are unaffected.

2.0.0 - 2024-10-18

This release is a complete rewrite of the crate, including reorganization of the code. The XXH3 algorithm now matches the 0.8 release of the reference C xxHash implementation.

Added

  • XxHash32::oneshot and XxHash64::oneshot can perform hashing with zero allocation and generally improved performance. If you have code that creates a hasher and hashes a slice of bytes exactly once, you are strongly encouraged to use the new functions. This might look like:

    // Before
    let mut hasher = XxHash64::new(); // or XxHash32, or with seeds
    some_bytes.hash(&mut hasher);
    let hash = hasher.finish();
    

    // After
    let hash = XxHash64::oneshot(some_bytes);

  • There is a feature flag for each hashing implementation. It is recommended that you opt-out of the crate's default features and only select the implementations you need to improve compile speed.

Changed

  • The crates minimum supported Rust version (MSRV) is now 1.81.

  • Functional and performance comparisons are made against the reference C xxHash library version 0.8.2, which includes a stable XXH3 algorithm.

  • Support for randomly-generated hasher instances is now behind the random feature flag. It was previously combined with the std

... (truncated)

Commits
  • 725da3f Release version 2.0.1
  • dfdffb7 Update the changelog
  • b937bc2 Merge pull request #103 from shepmaster/maint
  • bd2341a Consistently case xxHash algorithm in documentation
  • a00a078 Check for formatting errors in CI
  • bbfa771 Merge pull request #102 from shepmaster/non-wrapping-panic
  • 9237e27 Test with minimum and maximum seed values
  • 75f9e5f Update the changelog
  • 3d925b4 Release version 2.0.0
  • 872959e Merge pull request #101 from shepmaster/v2
  • Additional commits viewable in compare view


Dependabot compatibility score

You can trigger a rebase of this PR 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 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[bot] commented 2 weeks ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.