CK_ARRAY_INITIALIZED(3)

💖 CK_ARRAY_INITIALIZED 💖

okay bestie, welcome to the ck_array_initialized(3) page, it's a whole manual page from the Concurrency Kit and it's lowkey iconic 🎀

✨ NAME ✨

ck_array_initialized — it tells you whether an array was recently initialized or deinitialized 🦋

📚 LIBRARY 📚

Concurrency Kit — that's libck, link it with -lck 💅

🌸 SYNOPSIS 🌸

#include <ck_array.h>

bool
ck_array_initialized(ck_array_t *array);

like yes bestie, that's the whole vibe ✨

🫶 DESCRIPTION 🫶

so ck_array_initialized(3) is the function you call when you need to figure out whether an array was recently initialized with ck_array_init(3), or deinitialized with ck_array_deinit(3). it's giving detective energy fr fr 🔍

⚠️ but bestie, listen — behavior is undefined if a user allocates internal allocator data in through other means. like, do not do that. no cap. 💀

👑 RETURN VALUES 👑

• it returns true if the array is initialized ✨
• and false otherwise 🙈

that's it, that's the tea ☕ periodt

🔥 SEE ALSO 🔥

• ck_array_commit(3)
• ck_array_put(3)
• ck_array_put_unique(3)
• ck_array_remove(3)
• ck_array_init(3)
• ck_array_deinit(3)
• ck_array_length(3)
• ck_array_buffer(3)
• CK_ARRAY_FOREACH(3)

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

💖 and that's the whole page bestie, mwah 💖

this lil icon was dated October 18, 2013, and it's part of the Concurrency Kit situation, section 3 of the manuals 🎀 slay, bye 💅✨