aHash
aHash copied to clipboard
aHash is a non-cryptographic hashing algorithm that uses the AES hardware instruction
Not a bug, this is just FYI. Given how common the use of `rayon` is, this is something you may wish to provide documentation for, or even implementations of the...
Updating crates.io index error: cyclic package dependency: package `ahash v0.7.4` depends on itself. Cycle: package `ahash v0.7.4` ... which is depended on by `hashbrown v0.11.2` ... which is depended on...
Rust recently added `into_keys` and `into_values` that consume `self` and return an iterator over the moved keys or values. This doesn't work with AHashMap because the new functions are used...
Please tag releases in git, to help ease correlating with Cargo releases.
The current documentation (Version 0.7.6) makes only very little mention that aHash fundamentally requires a special hardware instruction set. Specifically -- for the uninitiated -- it does not become clear...
Not sure where this should be reported, but I figured this crate might be a good starting point. Please let me know if it doesn't fit. While looking into an...
They recently defined microarchitecture levels for x86-64 ([Wikipedia](https://en.wikipedia.org/wiki/X86-64#Microarchitecture_levels)) but apparently decided against including AES in any of them. So it seems like applications may in the future start targeting these...
https://crates.io/crates/rustc-hash I'd be curious to see how things compare. Their docs say they outperform FNV, which is promising.
This is especially useful for no_std development, where we don't want to introduce the getrandom dependency. After this change, one can choose to disable random-state feature and implement their own...
As a feature request, it would be quite nice to be able to use `compile-time-rng` (or, better, some `dummy-unsafe-no-rng` cfg) when building binaries with hashbrown maps while fuzzing. The https://github.com/rust-fuzz...