CK_HT_ENTRY_KEY_SET(3)
π CK_HT_ENTRY_KEY_SET(3) π
okay so bestie, welcome to ck_ht_entry_key_set(3) β a manual page from the Concurrency Kit era, and yes we're doing this in the library that lives at libck (link it with -lck, mwah π
).
β¨ NAME β¨
ck_ht_entry_key_set β set up a pointer to a key inside a hash table entry, no cap π«Ά
π LIBRARY π
Concurrency Kit (that's libck, and you link it with -lck) πΈ
π SYNOPSIS π
#include <ck_ht.h>
void
ck_ht_entry_key_set(ck_ht_entry_t *entry, const void *key,
uint16_t key_length);
π¦ DESCRIPTION π¦
so like, ck_ht_entry_key_set() takes the object that entry points at and initializes it with a key, and that key is whatever key points at. the length of that key? that's your key_length argument, periodt β¨
the biggest value key_length is allowed to be is defined by the CK_HT_KEY_LENGTH macro. that's the ceiling, bestie, don't go past it π
this function is typically used to initialize an entry for ck_ht_get_spmc(3) and ck_ht_remove_spmc(3) operations β those are the moments it really shines, main character energy honestly π
and it's expected that the entry is gonna be associated with a hash table that was initialized with CK_HT_MODE_BYTESTRING. if you want the whole story on that, go peek at ck_ht_init(3) π§
π« RETURN VALUES π«
ck_ht_entry_key_set() has no return value. it gives you nothing back. it's giving void. and that's iconic of it πβ¨
π ERRORS π
this function will never fail. not once. not ever. it simply cannot and will not do you like that π«Ά
π SEE ALSO π
the whole friend group, fr fr:
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_direct(3)ck_ht_entry_key(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)
and if you want even more, there's extra info waiting at http://concurrencykit.org/ π¦
okay that's the whole page, you ate that π
the version is CK_HT_ENTRY_KEY_SET(3) and it's dated March 30, 2012 β yeah she's an elder but she's still slaying, and she's from the Concurrency Kit source. bye bestie, go set some keys ππΈβ¨
π¦ where this page comes from
- alpine 3.24: ck-doc 0.7.2-r1 Β· BSD-2-Clause AND Apache-2.0
- debian bookworm: libck-dev 0.7.1-10 Β· BSD-2-Clause
- debian trixie: libck-dev 0.7.2-6 Β· BSD-2-Clause
- epel 10: ck-devel 0.7.2-1.el10_1 Β· BSD-2-clause AND Apache-2.0 AND BSD-3-clause
- epel 9: ck-devel 0.7.0-10.el9 Β· BSD
- fedora 43: ck-devel 0.7.2-2.fc43 Β· BSD-2-clause AND Apache-2.0 AND BSD-3-clause
- fedora 43: ck-devel 0.7.2-2.fc43 Β· BSD-2-clause AND Apache-2.0 AND BSD-3-clause
- fedora 44: ck-devel 0.7.2-4.fc44 Β· BSD-2-clause AND Apache-2.0 AND BSD-3-clause
- fedora 44: ck-devel 0.7.2-4.fc44 Β· BSD-2-clause AND Apache-2.0 AND BSD-3-clause
- nixos 26.05: ck 0.7.2
- nixpkgs unstable: ck 0.7.2
- opensuse-leap 16.0: ck-devel 0.7.2-bp160.1.9 Β· Apache-2.0 AND BSD-2-Clause
- opensuse-leap 16.0: ck-devel 0.7.2-bp160.1.9 Β· Apache-2.0 AND BSD-2-Clause
- opensuse-leap 16.0: ck-devel 0.7.2-bp160.1.9 Β· Apache-2.0 AND BSD-2-Clause
- ubuntu jammy: libck-dev 0.7.1-6ubuntu2 Β· BSD-2-Clause
- ubuntu noble: libck-dev 0.7.1-13build1 Β· BSD-2-Clause
- ubuntu questing: libck-dev 0.7.2-5ubuntu1
- ubuntu resolute: libck-dev 0.7.2-5ubuntu2 Β· BSD-2-Clause
- ubuntu stonking: libck-dev 0.7.2-11 Β· BSD-2-Clause
- Copyright 2012-2013 Samy Al Bahra
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms