hashmap: provide deallocation function names
hashmap_free(), hashmap_free_entries(), and hashmap_free_() have existed
for a while, but aren't necessarily the clearest names, especially with
hashmap_partial_clear() being added to the mix and lazy-initialization
now being supported. Peff suggested we adopt the following names[1]:
- hashmap_clear() - remove all entries and de-allocate any
hashmap-specific data, but be ready for reuse
- hashmap_clear_and_free() - ditto, but free the entries themselves
- hashmap_partial_clear() - remove all entries but don't deallocate
table
- hashmap_partial_clear_and_free() - ditto, but free the entries
This patch provides the new names and converts all existing callers over
to the new naming scheme.
[1] https://lore.kernel.org/git/20201030125059.GA3277724@coredump.intra.peff.net/
Signed-off-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
committed by
Junio C Hamano
parent
33f20d8217
commit
6da1a25814
2
oidmap.c
2
oidmap.c
@@ -27,7 +27,7 @@ void oidmap_free(struct oidmap *map, int free_entries)
|
||||
return;
|
||||
|
||||
/* TODO: make oidmap itself not depend on struct layouts */
|
||||
hashmap_free_(&map->map, free_entries ? 0 : -1);
|
||||
hashmap_clear_(&map->map, free_entries ? 0 : -1);
|
||||
}
|
||||
|
||||
void *oidmap_get(const struct oidmap *map, const struct object_id *key)
|
||||
|
||||
Reference in New Issue
Block a user