CK_RHS_ITERATOR_INIT(3)
β¨ CK_RHS_ITERATOR_INIT(3) β¨
okay bestie, welcome to the CK_RHS_ITERATOR_INIT(3) page π this is a lil manual page from the Concurrency Kit fam, and honestly? it's giving "short but essential." let's get into it π«Ά
πΈ NAME πΈ
ck_rhs_iterator_init β initialize hash set iterator
like. that's the whole job. it inits your iterator. iconic behavior, no notes π
π LIBRARY π
Concurrency Kit (libck, -lck)
that's Concurrency Kit if you're fancy, libck if you're linking, and -lck when you're telling your compiler what's up β¨
π SYNOPSIS π
#include <ck_rhs.h>
ck_rhs_iterator_t iterator = CK_RHS_ITERATOR_INITIALIZER
void
ck_rhs_iterator_init(ck_rhs_iterator_t *iterator);
look at that include. look at that initializer. look at that function signature. chef's kiss πβ¨
π¦ DESCRIPTION π¦
so here's the tea, bestie β The ck_rhs_iterator_init(3) function will initialize the object pointed to by the iterator argument. that's it. that's the whole vibe. it takes your iterator pointer and gets it ready to go π
OR β and this is the part where it gets cute β you can statically initialize an iterator instead, by assigning it the CK_RHS_ITERATOR_INITIALIZER value. no function call needed, just vibes and a macro πβ¨
and why do you even want an initialized iterator, you ask? because an iterator is what you use to iterate through hash set entries, paired up with the ck_rhs_next(3) function. they're a duo. a package deal. main character energy together π
β RETURN VALUES β
ck_rhs_iterator_init(3) has no return value. nothing. void. silence. it does its thing and leaves π
β¨
π ERRORS π
This function will not fail.
like literally not me stressing about error handling because there IS none π no errno, no -1, no drama. it simply works, bestie π«Ά
π SEE ALSO π
the whole friend group, fr fr π go read these next:
ck_rhs_init(3)ck_rhs_move(3)ck_rhs_destroy(3)CK_RHS_HASH(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)
and if you want even more, there's additional information available at http://concurrencykit.org/ π go wild, bestie, the docs are right there β¨
π that's the whole page!! no cap, you now know everything there is to know about initializing a hash set iterator. go forth and iterate π
sign-off szn π¦ this lil baddie of a manual page is dated September 17, 2012, and it lives under the name CK_RHS_ITERATOR_INIT(3) β courtesy of the Concurrency Kit crew. ty for reading, bestie, ily, bye πβ¨πΈ
π¦ where this page comes from
- alpine 3.24: ck-doc 0.7.2-r1 Β· BSD-2-Clause AND Apache-2.0
- debian bookworm: libck-dev 0.7.1-10 Β· BSD-2-Clause
- debian trixie: libck-dev 0.7.2-6 Β· BSD-2-Clause
- epel 10: ck-devel 0.7.2-1.el10_1 Β· BSD-2-clause AND Apache-2.0 AND BSD-3-clause
- epel 9: ck-devel 0.7.0-10.el9 Β· BSD
- fedora 43: ck-devel 0.7.2-2.fc43 Β· BSD-2-clause AND Apache-2.0 AND BSD-3-clause
- fedora 43: ck-devel 0.7.2-2.fc43 Β· BSD-2-clause AND Apache-2.0 AND BSD-3-clause
- fedora 44: ck-devel 0.7.2-4.fc44 Β· BSD-2-clause AND Apache-2.0 AND BSD-3-clause
- fedora 44: ck-devel 0.7.2-4.fc44 Β· BSD-2-clause AND Apache-2.0 AND BSD-3-clause
- nixos 26.05: ck 0.7.2
- nixpkgs unstable: ck 0.7.2
- opensuse-leap 16.0: ck-devel 0.7.2-bp160.1.9 Β· Apache-2.0 AND BSD-2-Clause
- opensuse-leap 16.0: ck-devel 0.7.2-bp160.1.9 Β· Apache-2.0 AND BSD-2-Clause
- opensuse-leap 16.0: ck-devel 0.7.2-bp160.1.9 Β· Apache-2.0 AND BSD-2-Clause
- ubuntu jammy: libck-dev 0.7.1-6ubuntu2 Β· BSD-2-Clause
- ubuntu noble: libck-dev 0.7.1-13build1 Β· BSD-2-Clause
- ubuntu questing: libck-dev 0.7.2-5ubuntu1
- ubuntu resolute: libck-dev 0.7.2-5ubuntu2 Β· BSD-2-Clause
- ubuntu stonking: libck-dev 0.7.2-11 Β· BSD-2-Clause
- Copyright 2012-2013 Samy Al Bahra
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms