add a hashtable implementation that supports O(1) removal
commitfa0bc514cabc19dbd1d873a9a133977c26c5c6c5
authorKarsten Blees <karsten.blees@gmail.com>
Thu, 14 Nov 2013 19:17:54 +0000 (14 20:17 +0100)
committerStepan Kasal <kasal@ucw.cz>
Wed, 16 Apr 2014 14:33:45 +0000 (16 16:33 +0200)
tree77d02bb41826676e0826b0ddea30325310560e34
parentfc48c50837c26a0039cbc81a27f9002fe5f16895
add a hashtable implementation that supports O(1) removal

The existing hashtable implementation (in hash.[ch]) uses open addressing
(i.e. resolve hash collisions by distributing entries across the table).
Thus, removal is difficult to implement with less than O(n) complexity.
Resolving collisions of entries with identical hashes (e.g. via chaining)
is left to the client code.

Add a hashtable implementation that supports O(1) removal and is slightly
easier to use due to builtin entry chaining.

Supports all basic operations init, free, get, add, remove and iteration.

Also includes ready-to-use hash functions based on the public domain FNV-1
algorithm (http://www.isthe.com/chongo/tech/comp/fnv).

The per-entry data structure (hashmap_entry) is piggybacked in front of
the client's data structure to save memory. See test-hashmap.c for usage
examples.

The hashtable is resized by a factor of four when 80% full. With these
settings, average memory consumption is about 2/3 of hash.[ch], and
insertion is about twice as fast due to less frequent resizing.

Lookups are also slightly faster, because entries are strictly confined to
their bucket (i.e. no data of other buckets needs to be traversed).

Signed-off-by: Karsten Blees <blees@dcon.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/technical/api-hashmap.txt [new file with mode: 0644]
Makefile
hashmap.c [new file with mode: 0644]
hashmap.h [new file with mode: 0644]
t/t0011-hashmap.sh [new file with mode: 0755]
test-hashmap.c [new file with mode: 0644]