From: Junio C Hamano <gitster@pobox.com>
To: Brandon Williams <bmwill@google.com>
Cc: git@vger.kernel.org, Johannes.Schindelin@gmx.de
Subject: Re: [PATCH] oidmap: ensure map is initialized
Date: Wed, 27 Dec 2017 10:01:59 -0800 [thread overview]
Message-ID: <xmqqtvwcnj6w.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20171222232729.253936-1-bmwill@google.com> (Brandon Williams's message of "Fri, 22 Dec 2017 15:27:29 -0800")
Brandon Williams <bmwill@google.com> writes:
> Ensure that an oidmap is initialized before attempting to add, remove,
> or retrieve an entry by simply performing the initialization step
> before accessing the underlying hashmap.
>
> Signed-off-by: Brandon Williams <bmwill@google.com>
> ---
Looks sane. Thanks for illustrating the idea with actual code.
Essentially, you are using map->map.cmpfn as a boolean to see "have
we initialized this thing? if not, we need to initialize it on
demand".
By the way, I am somewhat more sympathetic than usual to Dscho's
"make oidmap_get() very aware of the internal implementation detail
of hashmap_get_from_hash() to micro-optimize by removing the check
from _get()". Such a layering violation is disgusting, and making
it deliberately shows an even worse design taste, but in this
particular case, because the oidmap API is too thin a layer on top
of hashmap, it is understandably a very tempting approach.
> oidmap.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/oidmap.c b/oidmap.c
> index 6db4fffcd..d9fb19ba6 100644
> --- a/oidmap.c
> +++ b/oidmap.c
> @@ -33,12 +33,19 @@ void oidmap_free(struct oidmap *map, int free_entries)
>
> void *oidmap_get(const struct oidmap *map, const struct object_id *key)
> {
> + if (!map->map.cmpfn)
> + return NULL;
> +
> return hashmap_get_from_hash(&map->map, hash(key), key);
> }
>
> void *oidmap_remove(struct oidmap *map, const struct object_id *key)
> {
> struct hashmap_entry entry;
> +
> + if (!map->map.cmpfn)
> + oidmap_init(map, 0);
> +
> hashmap_entry_init(&entry, hash(key));
> return hashmap_remove(&map->map, &entry, key);
> }
> @@ -46,6 +53,10 @@ void *oidmap_remove(struct oidmap *map, const struct object_id *key)
> void *oidmap_put(struct oidmap *map, void *entry)
> {
> struct oidmap_entry *to_put = entry;
> +
> + if (!map->map.cmpfn)
> + oidmap_init(map, 0);
> +
> hashmap_entry_init(&to_put->internal_entry, hash(&to_put->oid));
> return hashmap_put(&map->map, to_put);
> }
next prev parent reply other threads:[~2017-12-27 18:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 10:59 [PATCH] oidmap.h: strongly discourage using OIDMAP_INIT directly Johannes Schindelin
2017-12-22 17:16 ` Brandon Williams
2017-12-22 20:12 ` Junio C Hamano
2017-12-22 23:27 ` [PATCH] oidmap: ensure map is initialized Brandon Williams
2017-12-23 0:23 ` Johannes Schindelin
2017-12-27 18:01 ` Junio C Hamano [this message]
2017-12-23 0:15 ` [PATCH] oidmap.h: strongly discourage using OIDMAP_INIT directly Johannes Schindelin
2018-01-02 18:13 ` Jeff Hostetler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqtvwcnj6w.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=bmwill@google.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).