diff options
author | Elijah Newren <newren@gmail.com> | 2020-10-13 03:40:41 +0300 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2020-10-13 23:06:37 +0300 |
commit | 6474b869393b2d40b6e1b3ab5633ce2bad6abe48 (patch) | |
tree | 5cd8cc64989424c943e5d6138b3c5c8722cded72 /hashmap.c | |
parent | d4a392452e292ff924e79ec8458611c0f679d6d4 (diff) |
hashmap: add usage documentation explaining hashmap_free[_entries]()
The existence of hashmap_free() and hashmap_free_entries() confused me,
and the docs weren't clear enough. We are dealing with a map table,
entries in that table, and possibly also things each of those entries
point to. I had to consult other source code examples and the
implementation. Add a brief note to clarify the differences. This will
become even more important once we introduce a new
hashmap_partial_clear() function which will add the question of whether
the table itself has been freed.
Signed-off-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'hashmap.c')
0 files changed, 0 insertions, 0 deletions