CK_HS_MOVE(3)

💖 ck_hs_move(3) — move one from hash set to another 💖

okay bestie, gather round, because this little function is lowkey a whole vibe shift for your hash sets 🦋

📚 LIBRARY

Concurrency Kit (that's libck, link it with -lck) 💅

✨ SYNOPSIS ✨

#include <ck_hs.h>

bool
ck_hs_move(ck_hs_t *destination, ck_hs_t *source,
    ck_hs_hash_cb_t *hash_cb, ck_hs_compare_cb_t *compare_cb,
    struct ck_malloc *m);

no cap, that's the whole signature. five args. she's efficient. 👑

🌸 DESCRIPTION 🌸

so the tea is: ck_hs_move(3) will initialize source from destination. yep, that's the direction, don't come for me, that's literally what the page says. 🫶

while she's doing that, the hash function gets set to hash_cb, the comparison function gets set to compare_cb, and the allocator callbacks get set to m. it's giving "glow up with a whole new callback wardrobe." ✨

🚨 bestie, listen: further modifications to source will result in undefined behavior. like, don't. it's not a "try it and see" situation, it's a "put the keyboard down" situation. 😭

but here's the good news — concurrent ck_hs_get(3) and ck_hs_fas(3) operations to source are legal until the next write operation to destination. read-only girlies, you're safe. 💖

what is this actually doing though? this operation moves ownership from one hash set object to another, and re-assigns callback functions to developer-specified values. slay. that means you get dynamic configuration of allocation callbacks, which is necessary for use-cases involving executable code which may be unmapped underneath the hash set. (imagine your code getting yanked out from under you mid-hash — yeah, that's why this exists. main character problem-solving energy, fr fr. 🧚)

🎀 RETURN VALUES 🎀

• upon successful completion, ck_hs_move(3) returns true — ate, no crumbs 🍓
• otherwise it returns false to indicate an error — not the vibe, but at least she tells you 💀

👀 SEE ALSO 👀

the whole friend group, in order, because they roll together:

• ck_hs_init(3)
• ck_hs_destroy(3)
• CK_HS_HASH(3)
• ck_hs_iterator_init(3)
• ck_hs_next(3)
• ck_hs_put(3)
• ck_hs_put_unique(3)
• ck_hs_set(3)
• ck_hs_fas(3)
• ck_hs_remove(3)
• ck_hs_grow(3)
• ck_hs_rebuild(3)
• ck_hs_gc(3)
• ck_hs_count(3)
• ck_hs_reset(3)
• ck_hs_reset_size(3)
• ck_hs_stat(3)

additional information available at http://concurrencykit.org/ 🌈

mwah, that's a wrap bestie 💜 this one dropped July 18, 2013 and it lives in the CK_HS_MOVE(3) corner of the manual, brought to you by the Concurrency Kit girlies. periodt. 💅✨