CK_HT_ENTRY_KEY(3)

💖 CK_HT_ENTRY_KEY — ok bestie let's get ur key back 💖

So like, ck_ht_entry_key(3) is the manual page, and she lives in the Concurrency Kit library, aka libck, which you link with -lck. 🌸

✨ NAME ✨

ck_ht_entry_key — return pointer to key as specified in hash table entry 🔑✨

📚 LIBRARY 📚

Concurrency Kit (libck, -lck) 🫶

🎀 SYNOPSIS 🎀

#include <ck_ht.h>

void *
ck_ht_entry_key(ck_ht_entry_t *entry);

🦋 DESCRIPTION 🦋

Okay so real talk. The ck_ht_entry_key() function will return the key pointer as specified in the object pointed to by the entry argument. That's it. That's the whole job. She's giving "hand u the key, no questions asked" energy 💅

Heads up though! It is expected that the entry is associated with a hash table initialized with CK_HT_MODE_BYTESTRING — go peek at ck_ht_init(3) if u need the lore on that one 📖

🌈 RETURN VALUES 🌈

ck_ht_entry_key() returns NULL if the entry is empty. Empty entry = no key = NULL, periodt. 💀

💀 ERRORS 💀

Behavior is undefined if entry has not been initialized. Not "weird", not "kinda buggy" — undefined. Like, do not pass her an uninitialized entry, that is NOT the vibe, i'm begging u 😭🙈

👑 SEE ALSO 👑

The whole bestie squad, in order:

• ck_ht_stat(3)
• ck_ht_init(3)
• ck_ht_destroy(3)
• ck_ht_hash(3)
• ck_ht_hash_direct(3)
• ck_ht_set_spmc(3)
• ck_ht_put_spmc(3)
• ck_ht_gc(3)
• ck_ht_get_spmc(3)
• ck_ht_grow_spmc(3)
• ck_ht_remove_spmc(3)
• ck_ht_count(3)
• ck_ht_reset_spmc(3)
• ck_ht_reset_size_spmc(3)
• ck_ht_entry_empty(3)
• ck_ht_entry_key_set(3)
• ck_ht_entry_key_set_direct(3)
• ck_ht_entry_key_length(3)
• ck_ht_entry_value(3)
• ck_ht_entry_set(3)
• ck_ht_entry_set_direct(3)
• ck_ht_entry_key_direct(3)
• ck_ht_entry_value_direct(3)
• ck_ht_iterator_init(3)
• ck_ht_next(3)

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

And that's a wrap, bestie! This page is dated March 30, 2012, and it's page CK_HT_ENTRY_KEY(3) of the manual — go forth and grab ur keys responsibly 🫶💖✨