CK_BITMAP_ITERATOR_INIT(3)

💖 CK_BITMAP_ITERATOR_INIT — initialize bitmap iterator 💖

okay bestie so this is a Concurrency Kit page, aka libck, and you link it with -lck. it's a tiny little function but it's the main character of getting your bitmap loop started, so let's go 🦋

✨ SYNOPSIS ✨

#include <ck_ht.h>

void
ck_bitmap_iterator_init(ck_bitmap_iterator_t *iterator,
    ck_bitmap_t *bitmap);

that's it. two args. no drama. 💅

🌸 DESCRIPTION 🌸

so ck_bitmap_iterator_init() initializes the object that iterator points at, and it sets it up to be used with bitmap. like, you're basically introducing them to each other. matchmaker era 🎀

and why do you even want an iterator, you ask? because an iterator is what you use to iterate through the set bits of a bitmap — and you do that with the ck_bitmap_next(3) function. so this init call is literally the first step of that whole journey. no init, no next, no bits. iykyk ✨

fr fr, this function is the setup, and ck_bitmap_next(3) is the payoff. you need both. don't skip the glow-up phase 🫶

💜 RETURN VALUES 💜

ck_bitmap_iterator_init() does not return a value. it's void, bestie. it just does the thing and leaves. no receipts, no return slip. iconic behavior honestly 😌

🧚 ERRORS 🧚

this function will not fail. not even a little. no error codes, no drama, no "whoops bestie". it simply cannot flop 💀✨

🌈 SEE ALSO 🌈

• ck_bitmap_base(3)
• ck_bitmap_size(3)
• ck_bitmap_init(3)
• ck_bitmap_set(3)
• ck_bitmap_reset(3)
• ck_bitmap_clear(3)
• ck_bitmap_bits(3)
• ck_bitmap_buffer(3)
• ck_bitmap_next(3)

more lore is available at http://concurrencykit.org/ — go read, bestie, it's giving homework but the fun kind 📚💖

and that's the whole page!! this one came from April 27, 2012 and it's page CK_BITMAP_ITERATOR_INIT(3) of the Concurrency Kit manual. mwah, slay, go iterate those bits 💅🌸⭐