CK_PR_NOT(3)

✨ ck_pr_not(3) — the atomic complement glow-up ✨

okay bestie, gather round, because we're talking about ck_pr_not 💅 — well, technically the whole ck_pr_not family, which is a lil squad of nine functions: ck_pr_not_ptr, ck_pr_not_double, ck_pr_not_char, ck_pr_not_uint, ck_pr_not_int, ck_pr_not_64, ck_pr_not_32, ck_pr_not_16, and ck_pr_not_8. they do atomic complement operations. that's the whole vibe. that's the whole girl. 🎀

🌸 LIBRARY 🌸

she lives in Concurrency Kit, aka libck, and you link her with -lck. periodt. 🫶

✨ SYNOPSIS ✨

first things first, you gotta let her in:

#include <ck_pr.h>

then pick your fighter, one signature at a time:

void
ck_pr_not_ptr(void *target);

void
ck_pr_not_double(double *target);

void
ck_pr_not_char(char *target);

void
ck_pr_not_uint(unsigned int *target);

void
ck_pr_not_int(int *target);

void
ck_pr_not_64(uint64_t *target);

void
ck_pr_not_32(uint32_t *target);

void
ck_pr_not_16(uint16_t *target);

void
ck_pr_not_8(uint8_t *target);

like, nine whole entry points, one for every type you could possibly be obsessed with. 🔥

💖 DESCRIPTION 💖

so the ck_pr_not(3) family of functions atomically complement the value pointed to by target.

that's it. that's the tea. 🍓

"complement" meaning the bitwise flip — the ~ energy — and "atomically" meaning nobody can sneak in halfway through and catch it looking messy. the whole flip lands as one single, unbothered, iconic operation. no torn reads, no half-flipped chaos. main character energy only. 👑

🦋 RETURN VALUES 🦋

these functions have no return value. they're void. they give you nothing back because they already gave you everything. 💀 (respectfully!!)

🌈 SEE ALSO 🌈

go read these next, i promise they're all bangers:

• ck_pr_fence_load(3)
• ck_pr_fence_load_depends(3)
• ck_pr_fence_store(3)
• ck_pr_fence_memory(3)
• ck_pr_load(3)
• ck_pr_store(3)
• ck_pr_fas(3)
• ck_pr_faa(3)
• ck_pr_inc(3)
• ck_pr_not(3)
• ck_pr_neg(3)
• ck_pr_add(3)
• ck_pr_sub(3)
• ck_pr_and(3)
• ck_pr_or(3)
• ck_pr_xor(3)
• ck_pr_cas(3)
• ck_pr_btc(3)
• ck_pr_bts(3)
• ck_pr_btr(3)

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

not me writing a whole love letter to a bitwise NOT. anyway. iykyk. 🧚

okay bye bestie, this page was dated April 7, 2013 and it's filed under ck_pr_not(3) — catch you in the next manpage, mwah 💜🌸🎀