diff options
author | Jeff King <peff@peff.net> | 2016-08-22 17:57:53 -0400 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2016-08-23 14:45:29 -0700 |
commit | 4a5397ca79f895e84b3a28abe3ab2e8a0faf3510 (patch) | |
tree | 00b40f45de7b8f4ae74e3afce5b3d0e7e59c1d49 /utf8.c | |
parent | cache_or_unpack_entry: drop keep_cache parameter (diff) | |
download | tgif-4a5397ca79f895e84b3a28abe3ab2e8a0faf3510.tar.xz |
clear_delta_base_cache_entry: use a more descriptive name
The delta base cache entries are stored in a fixed-length
hash table. So the way to remove an entry is to "clear" the
slot in the table, and that is what this function does.
However, the name is a leaky abstraction. If we were to
change the hash table implementation, it would no longer be
about "clearing". We should name it after _what_ it does,
not _how_ it does it. I.e., something like "remove" instead
of "clear".
But that does not tell the whole story, either. The subtle
thing about this function is that it removes the entry, but
does not free the entry data. So a more descriptive name is
"detach"; we give ownership of the data buffer to the
caller, and remove any other resources.
This patch uses the name detach_delta_base_cache_entry().
We could further model this after functions like
strbuf_detach(), which pass back all of the detached
information. However, since there are so many bits of
information in the struct (the data, the size, the type),
and so few callers (only one), it's not worth that
awkwardness. The name change and a comment can make the
intent clear.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'utf8.c')
0 files changed, 0 insertions, 0 deletions