CK_RHS_NEXT(3)

✨ ck_rhs_next — iterate to next entry in hash set ✨

okay bestie, we're in the ck_rhs_next page from the Concurrency Kit manual, and honestly? it's giving "tiny function, big responsibilities" 💅

📚 LIBRARY

Concurrency Kit, aka libck, link it with -lck. that's the whole vibe. 🎀

🦋 SYNOPSIS

#include <ck_rhs.h>

bool
ck_rhs_next(ck_rhs_t *hs, ck_rhs_iterator_t *iterator, void **entry);

💖 DESCRIPTION

so ck_rhs_next(3) does one thing and it does it iconically: it bumps the iterator object that iterator points at, so it lands on the next non-empty hash set entry. like, it skips past all the empty slots because we do not have time for those. periodt.

and if ck_rhs_next(3) returns true? then the pointer that entry points at gets initialized to the current hash set key that the iterator object is sitting on. it's literally handing you the key. so generous of it. 🫶

⚠️ important, bestie: iterator is expected to have already been initialized using the ck_rhs_iterator_init(3) function, or statically initialized using CK_RHS_ITERATOR_INITIALIZER. you can't just roll up with a random uninitialized iterator and expect magic. that's not how any of this works. 🙈

🌸 RETURN VALUES

• if ck_rhs_next(3) returns true — slay! 🎉 the object that entry points at points to a valid hash set key. you're so back.
• if ck_rhs_next(3) returns false — oop 😭 the value of the object that entry points at is undefined. do not look at it. do not touch it. it's not for you.

💀 ERRORS

behavior is undefined if iterator or hs are uninitialized. like, genuinely undefined. no promises, no guarantees, no nothing. consider this your vibe check warning. 🚨

👑 SEE ALSO

the whole squad, fr fr:

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

and if you want even more lore, additional information is available at http://concurrencykit.org/ 🌈

okay that's the whole page, you ate it up 💅 this one's from September 17, 2012 (yes it's been iconic since 2012, we love an ageless queen) and it lives under the name CK_RHS_NEXT(3). go forth and iterate, bestie 🦋✨🎀