diff options
| author | Tyge Løvset <[email protected]> | 2020-06-22 21:20:00 +0200 |
|---|---|---|
| committer | GitHub <[email protected]> | 2020-06-22 21:20:00 +0200 |
| commit | 23e4aa6a3d3abe83600300660b9b5b30489cae6d (patch) | |
| tree | fdd50ae4ea942d9183b39a7a9a4ebd50b195afce | |
| parent | b46e55a30c0750b7dccecda8bd13b765501ccd1d (diff) | |
| download | STC-modified-23e4aa6a3d3abe83600300660b9b5b30489cae6d.tar.gz STC-modified-23e4aa6a3d3abe83600300660b9b5b30489cae6d.zip | |
Update README.md
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -99,7 +99,7 @@ The containers are memory efficent, i.e. they occupy as little memory as practic CHash and CVector discussion
----------------------------
-**CHash** is the most complex of the containers (although, currently only ~370 lines of code). It uses open hashing, but does not rely on power-of-two size table, nor prime number lengths, and it does not have tombstone buckets. Still, it is among the fastest hash-tables - see *Performance* below.
+**CHash** is the most complex of the containers (although, currently only ~370 lines of code). It uses open hashing, but does not rely on power-of-two size table, nor prime number lengths, and it does not have tombstone buckets. Still, it is among the fastest hash-tables, as shown above.
You may customize the destroy-, hash- and equals- function. It also supports a few other arguments in the declare-statement that allows to define a convertion from a raw/literal type to the key-type specified. This is handy when e.g. having CString as key, as it enables the usage of string literals as key in *put() and *get() functions, instead of requering a constructed CString. Without it you would need to write:
```
|
