CK_RHS_PUT_UNIQUE(3)

💖 ck_rhs_put_unique — the "no dupes allowed" hash set baddie 💖

ok bestie, welcome to ck_rhs_put_unique(3) — it's giving main character energy from the Concurrency Kit (that's libck, and you link it with -lck, iykyk). This one stores a key in a hash set and it is unconditionally doing it, no thoughts, no checking, no chill. 🦋

✨ SYNOPSIS ✨

#include <ck_rhs.h>

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

🌸 DESCRIPTION 🌸

so the way that ck_rhs_put_unique(3) works is: it stores the key you pass in key into the hash set that hs is pointing at. periodt. 💅

and listen — the key you hand over is expected to have the hash value you passed as hash. That hash? You already generated it earlier with the CK_RHS_HASH(3) macro. Don't skip that step bestie, it's literally the whole vibe. 🎀

If the call to ck_rhs_put(3) succeeded, then yes — your key is officially in the hash set pointed to by hs, slay. 🫶

⚠️ BUT. If a key with an equivalent value is already in the hash set, this function causes undefined behavior. Not a vibe. Not a warning. Just chaos. 💀

If you wanted replacement semantics — like, swap the old one out, new one in — that's a whole different girl, go look at ck_rhs_set(3) instead. 🙈

🔥 RETURN VALUES 🔥

• Success → ck_rhs_put_unique(3) returns true ✨
• Failure → it returns false 😭

💀 ERRORS 💀

• If key or hs are uninitialized → undefined behavior. Please initialize your stuff, I am begging. 🥺
• The function will also return false if the hash set could not be enlarged to accommodate the insertion of key. (yes, it tried to grow for you, it's an icon, it just couldn't)
• If you call this for a key value that's already been inserted → undefined behavior. again. it's giving "I warned you." 💅

🌈 SEE ALSO 🌈

the whole friend group, go say hi:

• 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_get(3)
• ck_rhs_put(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)

and if you want even more lore, the info is available at http://concurrencykit.org/ ⭐

ok that's the whole page bestie, you ate that 🍓 this was CK_RHS_PUT_UNIQUE(3), dated December 7, 2013, brought to you by the Concurrency Kit girlies. go forth and store those unique keys, but fr fr — no duplicates. mwah. 💖✨🧚