HASHKIT_JENKINS(3)

πŸ’– HASHKIT_JENKINS(3) πŸ’–

okay so bestie, welcome to the libmemcached-awesome corner of the manual pages β€” this one's hashkit_jenkins(3) and it's literally the whole libhashkit documentation vibe. buckle up πŸŽ€


✨ NAME ✨

hashkit_jenkins β€” libhashkit Documentation πŸ¦‹


🌸 SYNOPSIS 🌸

#include <libhashkit-1.0/hashkit.h>

Compile and link with -lhashkit πŸ‘‘

uint32_t hashkit_default(const char *key, size_t key_length)

uint32_t hashkit_fnv1_64(const char *key, size_t key_length)

uint32_t hashkit_fnv1a_64(const char *key, size_t key_length)

uint32_t hashkit_fnv1_32(const char *key, size_t key_length)

uint32_t hashkit_fnv1a_32(const char *key, size_t key_length)

uint32_t hashkit_crc32(const char *key, size_t key_length)

uint32_t hashkit_hsieh(const char *key, size_t key_length)

uint32_t hashkit_murmur(const char *key, size_t key_length)

uint32_t hashkit_murmur3(const char *key, size_t key_length)

uint32_t hashkit_jenkins(const char *key, size_t key_length)

uint32_t hashkit_md5(const char *key, size_t key_length)

πŸ’… DESCRIPTION πŸ’…

So these functions? They generate hash values from a key using a whole bunch of different algorithms. it's giving "choose your fighter" πŸ”₯

You can use them standalone, no cap β€” just call one and go. OR they'll get used automatically according to whatever algorithm you set with hashkit_set_function() or hashkit_set_distribution_function(). slay ✨

heads up bestie πŸ’€ β€” hashkit_hsieh(), hashkit_murmur() and hashkit_murmur3() are only available if the library is built with the appropriate flag enabled. so if they're ghosting you, that's why 😭

🫢 RETURN VALUE 🫢

A 32-bit hash value. that's it, that's the tea πŸ“


🌈 SEE ALSO 🌈


and that's the whole page, bestie β€” no crumbs left, periodt πŸ’œ

this lil' manual moment came to you from libmemcached-awesome, version 1.1, dated Jul 24, 2025. iconic behavior honestly πŸ‘‘βœ¨

πŸ“¦ where this page comes from