comparison: docs/Writerside/topics/hash_key.h.md
docs/Writerside/topics/hash_key.h.md
- branch
- docs/3.1
- changeset 1147
- 52802c36b261
- parent 1145
- 1a8fe7b7dd8a
equal
deleted
inserted
replaced
| 1146:151c057faf7c | 1147:52802c36b261 |
|---|---|
| 18 | 18 |
| 19 The primary function for creating a `CxHashKey` structure is `cx_hash_key()`. | 19 The primary function for creating a `CxHashKey` structure is `cx_hash_key()`. |
| 20 The other functions do effectively the same, but | 20 The other functions do effectively the same, but |
| 21 | 21 |
| 22 * `cx_hash_key_bytes()` is strongly typed if you want to avoid passing `void*` | 22 * `cx_hash_key_bytes()` is strongly typed if you want to avoid passing `void*` |
| 23 * `cx_hash_key_str()` conveniently takes a C string and computes the length on its own | 23 * `cx_hash_key_str()` conveniently takes a C string and computes the length |
| 24 * `cx_hash_key_cxstr()` conveniently takes a [UCX string](string.h.md) | 24 * `cx_hash_key_cxstr()` conveniently takes a [UCX string](string.h.md) |
| 25 | 25 |
| 26 In all cases, the hash will be available in the `hash` field of the returned structure. | 26 In all cases, the hash will be available in the `hash` field of the returned structure. |
| 27 | 27 |
| 28 <note> | 28 <note> |
