CK_BITMAP_SIZE(3)

💖 NAME 💖

ok so bestie, ck_bitmap_size — she tells you how many bytes you actually need for your bitmap. that's it, that's the whole job. returns necessary number of bytes for bitmap. slay.

📚 LIBRARY 📚

this one lives in the Concurrency Kit, aka libck, and you link it with -lck. iykyk 💅

✨ SYNOPSIS ✨

#include <ck_bitmap.h>

unsigned int
ck_bitmap_size(unsigned int n_bits);

that's the whole vibe. include the header, call the function, boom. 🎀

🌸 DESCRIPTION 🌸

ok so here's the tea: ck_bitmap_size() returns the number of bytes you need to allocate for a bitmap that's gonna hold the number of bits you specify in n_bits. it's literally just doing the math for you, bestie, so you don't have to.

when you're making bitmap objects dynamically — like, at runtime, with malloc energy — this is the function you call to figure out how many bytes to grab. 🧚

but listen: the object you allocate still has to be initialized with ck_bitmap_init(3). allocating it is NOT the same as initializing it. do both. no shortcuts. periodt. 🔥

don't skip the init step, bestie, i'm begging 😭

👑 RETURN VALUES 👑

this function returns a non-zero value. yes, always non-zero. no cap.

🦋 SEE ALSO 🦋

the whole friend group, in order:

• ck_bitmap_base(3)
• ck_bitmap_init(3)
• ck_bitmap_set_mpmc(3)
• ck_bitmap_reset_mpmc(3)
• ck_bitmap_test(3)
• ck_bitmap_clear(3)
• ck_bitmap_bits(3)
• ck_bitmap_buffer(3)

and if you want even more lore, it's all sitting at http://concurrencykit.org/ 🌈

k bye bestie, this page is from way back on April 22, 2012, and it's page CK_BITMAP_SIZE(3) — go allocate something iconic 💜✨