From 36d22d82aa202bb199967e9512281e9a53db42c9 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sun, 7 Apr 2024 21:33:14 +0200 Subject: Adding upstream version 115.7.0esr. Signed-off-by: Daniel Baumann --- third_party/rust/murmurhash3/README.rst | 50 +++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 third_party/rust/murmurhash3/README.rst (limited to 'third_party/rust/murmurhash3/README.rst') diff --git a/third_party/rust/murmurhash3/README.rst b/third_party/rust/murmurhash3/README.rst new file mode 100644 index 0000000000..d52ebd26e7 --- /dev/null +++ b/third_party/rust/murmurhash3/README.rst @@ -0,0 +1,50 @@ +************** +MurmurHash3.rs +************** + +.. image:: https://travis-ci.org/mhallin/murmurhash3-rs.svg?branch=master + :target: https://travis-ci.org/mhallin/murmurhash3-rs + +A rust implementation of the MurmurHash3_. Both 32 bit and 128 bit versions are included. The 128 +bit version is implemented with 64 bit datatypes, making it most suitable for x86_64 or other 64 bit +architectures. + +---- + +Usage +===== + +In your ``Cargo.toml``: + +.. code:: toml + + [dependencies] + murmurhash3 = "*" + +Then you can start to use either ``murmurhash3_x86_32`` or ``murmurhash3_x64_128``: + +.. code:: rust + + use murmurhash3::murmurhash3_x64_128; + + fn hash_value() { + let data = "test data"; + let seed = 48221234; + + let hash = murmurhash3_x64_128(data.as_bytes(), seed); + } + +Unfortunately, there is a bug in the ``HashState`` library implementation which prevents +implementation of new ``Hasher`` implementations for use in for example ``HashMap``. Additionally, +only the 32 bit hasher can be used there since ``HashMap`` uses a 64 bit hash internally. + +Tests +===== + +.. code:: + + cargo test + +Runs all tests with optimization level 3 in order to weed out potential problems with the optimizer. + +.. _MurmurHash3: https://code.google.com/p/smhasher/wiki/MurmurHash3 -- cgit v1.2.3