CK_EPOCH_END(3)

✨ ck_epoch_end ✨

okay bestie, welcome to ck_epoch_end from the CK_EPOCH_END(3) manual page 💖 this one is short and sweet and it's giving "the final bow after the main character moment." let's get into it 🎀

📚 LIBRARY

Concurrency Kit — that's libck, and you link it with -lck. yes, that's the whole vibe. 🦋

🌸 SYNOPSIS

#include <ck_epoch.h>

void
ck_epoch_end(ck_epoch_record_t *record, ck_epoch_section_t *section);

look at that signature, so clean, so demure 🫶

💅 DESCRIPTION

so here's the tea ☕ the ck_epoch_end(3) function marks the end of an epoch-protected code section. that's it. that's the job. you opened a protected section, and now you're closing it, like shutting the door behind you on your way out 🚪✨

and listen — section has to point to a section object that was initialized previously with ck_epoch_begin(3). like, you can't just show up with an uninitialized section and expect it to slay. that's not how any of this works, bestie 😭

no cap, the pairing here is ck_epoch_begin(3) ➡️ ck_epoch_end(3). they're a duo. a duo! do not separate them 💀

🎀 RETURN VALUES

literally nothing. it returns void. no value, no drama, no receipt. you get closure and that's it 💖

🙈 ERRORS

here's the part where you have to have done your homework first: the object pointed to by record must have been previously registered via ck_epoch_register(3).

like... if you skipped that step, that's on you, and it's not cute. register first, then end. in that order. periodt 👑

👀 SEE ALSO

the whole friend group, go read them all, i'm obsessed:

• ck_epoch_init(3)
• ck_epoch_register(3)
• ck_epoch_unregister(3)
• ck_epoch_recycle(3)
• ck_epoch_poll(3)
• ck_epoch_synchronize(3)
• ck_epoch_reclaim(3)
• ck_epoch_barrier(3)
• ck_epoch_call(3)
• ck_epoch_begin(3)

and for the girlies who want the full lore, additional information is available at http://concurrencykit.org/ 🌈⭐

k bye!! this page was dated September 2, 2012, and it's part of the Concurrency Kit docs — CK_EPOCH_END(3) forever 💜 mwah 🫶