CK_RHS_DESTROY(3)

💖 ck_rhs_destroy(3) — destroy hash set 💖

okay bestie, so this is a page from the Concurrency Kit manual, aka libck, and you link against it with -lck. It's the one about destroying a hash set. Not "delete one lil thing" — we're talking full teardown, the whole thing, gone. 💅

✨ SYNOPSIS ✨

#include <ck_rhs.h>

void
ck_rhs_destroy(ck_rhs_t *hs);

like, that's it. one function, one pointer, zero drama. 🎀

🌸 DESCRIPTION 🌸

So ck_rhs_destroy(3) goes and asks the underlying allocator — the exact one you specified when you set things up with ck_rhs_init(3) — to immediately destroy the object that hs points at. Immediately. No waiting around, no "in a sec", it's giving instant. 💀

⚠️ BIG ONE, no cap: the user must guarantee that no threads are accessing the object pointed to by hs when ck_rhs_destroy(3) is called. Like, that's on you. If some other thread is still poking at it while you're destroying it, that's not the function's problem, that's a you problem, and it's gonna be a bad time. 😭

🦋 RETURN VALUES 🦋

ck_rhs_destroy(3) has no return value. It returns nothing. Void. Empty. It simply does the thing and dips. ✨

🎀 ERRORS 🎀

This function is guaranteed not to fail. Periodt. 👑

🌈 SEE ALSO 🌈

the whole squad, fr fr:

• ck_rhs_init(3)
• ck_rhs_move(3)
• CK_RHS_HASH(3)
• ck_rhs_iterator_init(3)
• ck_rhs_next(3)
• ck_rhs_get(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)

More info is available at http://concurrencykit.org/ — go look, iykyk 🫶

and that's the whole page, bestie 💜 this lil gem comes to you from the Concurrency Kit crew, dated September 17, 2012, and the manual page itself is CK_RHS_DESTROY(3). slay, go free your memory responsibly 🌸💖