CK_EPOCH_INIT(3)

πŸ“¦
version 0.7.2 Β· 2 versions
, in alpine 3.24, debian trixie, epel 10, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ¦‹ NAME πŸ¦‹

okay so bestie, this is the manual page for ck_epoch_init(3) β€” the one and only initialize epoch reclamation object. She's giving setup energy, no cap. ✨

πŸ’– LIBRARY πŸ’–

Concurrency Kit β€” aka libck, linked with -lck. That's the whole squad. 🫢

✨ SYNOPSIS ✨

#include <ck_epoch.h>

void
ck_epoch_init(ck_epoch_t *epoch);

πŸŽ€ DESCRIPTION πŸŽ€

So ck_epoch_init() does exactly what it says on the tin: it initializes the epoch object pointed to by the epoch pointer. That's it. That's the function. She's the opening act for your epoch reclamation era. πŸ’…

🫢 RETURN VALUES 🫢

This function has no return value. None. Zero. It just initializes and leaves. Not me expecting a return value. 😭

πŸ’€ ERRORS πŸ’€

🚨 real talk: the behavior of ck_epoch_init() is undefined if epoch is not a pointer to a ck_epoch_t object. Like, undefined behavior. Do not pass her something random. That's not the vibe. πŸ’€

🌈 SEE ALSO 🌈

If you're obsessed and want more, go read these besties:

Additional information available at http://concurrencykit.org/


xoxo, your Unix bestie πŸ’… β€” this was CK_EPOCH_INIT(3), dated September 2, 2012, from the Concurrency Kit. slay, bye. πŸŽ€

πŸ“¦ where this page comes from