CK_HS_ITERATOR_INIT(3)

πŸ’– ck_hs_iterator_init β€” initialize hash set iterator

okay bestie, welcome to the CK_HS_ITERATOR_INIT(3) page, it's giving short-and-sweet and honestly? iconic. this is the little setup ritual you do before you loop through a hash set. no cap.


πŸ“š LIBRARY

this one lives in Concurrency Kit β€” that's libck, and you link it with -lck. mwah. πŸ’…


✨ SYNOPSIS ✨

#include <ck_hs.h>

ck_hs_iterator_t iterator = CK_HS_ITERATOR_INITIALIZER

void
ck_hs_iterator_init(ck_hs_iterator_t *iterator);

like, look at her. two whole ways to start an iterator and both are valid. we love options. πŸŽ€


🌸 DESCRIPTION 🌸

so the ck_hs_iterator_init(3) function initializes the object that iterator points at. that's the whole job. she's a one-task queen and she ate.

or, if you're feeling ✨static✨ about it, you can skip the function call entirely and just statically initialize your iterator by assigning it the CK_HS_ITERATOR_INITIALIZER value. literally just declare-and-go. no function call, no drama. πŸ¦‹

and what's the iterator for, you ask? it's the thing you use to walk through your hash set entries, hand-in-hand with the ck_hs_next(3) function. iterator + ck_hs_next(3) = the duo of the century, fr fr. πŸ‘‘


🫢 RETURN VALUES 🫢

ck_hs_iterator_init(3) has no return value. she returns void. nothing to check, nothing to unwrap. go in peace. 🌈


πŸ™ˆ ERRORS

this function will not fail. ever. zero. none. she does not know how. the vibe check is passed before you even get here. πŸ’€βœ¨


πŸ‘‘ SEE ALSO πŸ‘‘

the whole squad, bestie, all of them:

more lore available at http://concurrencykit.org/ 🧚


and that's the page, babe. go initialize something. πŸ“

Concurrency Kit (that's libck, linked with -lck, in case you forgot in the last 30 seconds), dated September 17, 2012 β€” and the manual name is CK_HS_ITERATOR_INIT(3) πŸ’– mwah, bye bestie! πŸ’œ

πŸ“¦ where this page comes from