CK_EPOCH_UNREGISTER(3)

💖 ck_epoch_unregister — bestie, it's time to clock out 🎀

okay so this is ck_epoch_unregister(3), a page from the Concurrency Kit manual, and it's literally the "you're done here, go home" button for epoch reclamation. no cap. ✨

🌸 LIBRARY 🌸

Concurrency Kit — that's libck, and you link it with -lck. 🫶

✨ SYNOPSIS ✨

#include <ck_epoch.h>

void
ck_epoch_unregister(ck_epoch_record_t *record);

💅 DESCRIPTION 💅

okay so the way that ck_epoch_unregister(3) works is: it lets the record that record points to be handed back out as a return value by ck_epoch_recycle(3). so basically you're putting your record back on the shelf so another thread of execution can come along and use it. main character energy for your record, honestly. 👑

🚨 warning bestie, dead serious: behavior is undefined if the object pointed to by record gets modified in any way — and yes, that includes even after you've already called ck_epoch_unregister(3). so hands off. don't touch it. don't look at it. it's not yours anymore. 😭

🦋 RETURN VALUES 🦋

this function has no return value. it just does the thing and dips. 💀

🌈 SEE ALSO 🌈

• ck_epoch_init(3)
• ck_epoch_register(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)
• ck_epoch_end(3)

Additional information available at http://concurrencykit.org/ — go peek, it's giving resources. 📚

and that's the whole page, bestie!! this one's dated September 2, 2012 and comes to you from Concurrency Kit — yeah she's an oldie but she's still iconic, periodt. now go unregister that record and live your truth. 💖✨🎀🦋