CK_HT_ENTRY_KEY_DIRECT(3)

✨ NAME ✨

ck_ht_entry_key_direct — bestie, this hands you back the key value exactly as it's specified in a hash table entry 💅

📚 LIBRARY 📚

Concurrency Kit (libck, link it with -lck) 🫶

🌸 SYNOPSIS 🌸

#include <ck_ht.h>

uintptr_t
ck_ht_entry_key_direct(ck_ht_entry_t *entry);

💖 DESCRIPTION 💖

Okay so ck_ht_entry_key_direct() returns the key value as specified in the object that entry points to. That's it. That's the whole job. Iconic behaviour, honestly. ✨

Heads up bestie: the entry is expected to be associated with a hash table that was initialized with CK_HT_MODE_DIRECT. Like, that's the vibe it was built for. Go peek at ck_ht_init(3) if you need the deets 👀

🎀 RETURN VALUES 🎀

• If the entry is empty, ck_ht_entry_key_direct() returns 0 🫥
• Otherwise, it returns the key value stored in the object that entry points to 🎉

💀 ERRORS 💀

Behavior is undefined if entry has not been initialized. Not "kinda weird", not "a little off" — undefined. So like… initialize your entries, bestie, I'm begging 😭

🌈 SEE ALSO 🌈

• 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(3)
• ck_ht_entry_value_direct(3)
• ck_ht_iterator_init(3)
• ck_ht_next(3)

More info is waiting for you at http://concurrencykit.org/ 🦋

And that's the whole page, bestie — this one's from the Concurrency Kit manual, dated March 30, 2012, filed under CK_HT_ENTRY_KEY_DIRECT(3). Go initialize your entries. Mwah 💋