| commit | a1100d2ceed75a9523981bfab607dedd2564ef8c | |
| author | Christian Couder <christian.couder@gmail.com> | |
| Sat, 15 Jun 2019 10:07:02 +0000 (15 12:07 +0200) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Tue, 18 Jun 2019 01:11:42 +0000 (17 18:11 -0700) | ||
| tree | d5a9a84ce7d5346219a8d4a9fbab3e835b5c7c12 | treesnapshot (tar.gz zip) |
| parent | 19cfa0e03316df26045c2f6d11ef860c2ca79a92 | commitdiff |
test-hashmap: remove 'hash' command
If hashes like strhash() are updated, for example to use a different
hash algorithm, we should not have to be updating t0011 to change out
the hashes.
As long as hashmap can store and retrieve values, and that it performs
well, we should not care what are the values of the hashes. Let's just
focus on the externally visible behavior instead.
Suggested-by: Jeff King <peff@peff.net>
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
If hashes like strhash() are updated, for example to use a different
hash algorithm, we should not have to be updating t0011 to change out
the hashes.
As long as hashmap can store and retrieve values, and that it performs
well, we should not care what are the values of the hashes. Let's just
focus on the externally visible behavior instead.
Suggested-by: Jeff King <peff@peff.net>
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| t/helper/test-hashmap.c | diffblobblamehistory | |
| t/t0011-hashmap.sh | diffblobblamehistory |