CK_RHS_GET(3)

💖 CK_RHS_GET(3) 💖

okay bestie, so this page lives in the Concurrency Kit manual, aka libck, and you link against it with -lck. We're talking about ck_rhs_get today and honestly? she's the finder. the girl who knows where everything is. let's go 🦋

✨ NAME ✨

ck_rhs_get — load a key from a hash set 💅

🌸 LIBRARY 🌸

Concurrency Kit (libck, -lck)

🎀 SYNOPSIS 🎀

#include <ck_rhs.h>

void *
ck_rhs_get(ck_rhs_t *hs, unsigned long hash, const void *key);

👑 DESCRIPTION 👑

so the ck_rhs_get(3) function is literally just gonna hand you back a pointer to a key inside the hash set hs — specifically a key that's of equivalent value to whatever object key is pointing at. it's giving "found her" energy fr fr.

now, plot twist: the key you pass in is expected to already have the hash value that you're handing over in the hash argument. and that hash? it's supposed to have been generated earlier using the CK_RHS_HASH(3) macro. don't just make one up, bestie, that's not the vibe. 🙈

🫶 RETURN VALUES 🫶

• if the key you gave is a member of hs, you get back a pointer to the key as it's stored inside hs. iconic. ✨
• if the key wasn't found in hs, you get NULL back. and that's it. that's the whole story. 💀

💀 ERRORS 💀

ngl this part is the scary part: behavior is undefined if entry or hs are uninitialized. like, uninitialized. do not do it. no cap. 😭

🌈 SEE ALSO 🌈

• ck_rhs_init(3)
• ck_rhs_move(3)
• ck_rhs_destroy(3)
• CK_RHS_HASH(3)
• ck_rhs_iterator_init(3)
• ck_rhs_next(3)
• ck_rhs_put(3)
• ck_rhs_put_unique(3)
• ck_rhs_set(3)
• ck_rhs_fas(3)
• ck_rhs_remove(3)
• ck_rhs_grow(3)
• ck_rhs_rebuild(3)
• ck_rhs_gc(3)
• ck_rhs_count(3)
• ck_rhs_reset(3)
• ck_rhs_reset_size(3)
• ck_rhs_stat(3)

there's also more lore waiting for you at http://concurrencykit.org/ — go drink your water and read the docs 💜

k that's the whole page bestie, hope it ate 🍓 this little masterpiece was dated September 17, 2012 and it's filed under CK_RHS_GET(3) in the Concurrency Kit collection. mwah, bye 💖✨