All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: A U Thor <shyamthakkar001@gmail.com>,
	 git@vger.kernel.org,  Christian Couder <chriscool@tuxfamily.org>,
	 Kaartic Sivaraam <kaartic.sivaraam@gmail.com>,
	 Josh Steadmon <steadmon@google.com>,
	Phillip Wood <phillip.wood123@gmail.com>
Subject: Re: [PATCH v4] t: port helper/test-hashmap.c to unit-tests/t-hashmap.c
Date: Wed, 31 Jul 2024 11:50:56 -0700	[thread overview]
Message-ID: <xmqq7cd12y5r.fsf@gitster.g> (raw)
In-Reply-To: <CAP8UFD04uQbWhY0QDp+nC8VyBvpUs=tBDm=w4CzKK2GcwFZdGQ@mail.gmail.com> (Christian Couder's message of "Wed, 31 Jul 2024 19:18:08 +0200")

Christian Couder <christian.couder@gmail.com> writes:

>>      +  const char *query[][2] = {
>>      +          { ignore_case ? "Key1" : "key1", "value1" },
>>      +          { ignore_case ? "keY2" : "key2", "value2" },
>>     -+          { ignore_case ? "foobarfrotz" : "fooBarFrotz", "value3" }
>>     ++          { ignore_case ? "FOObarFrotz" : "fooBarFrotz", "value3" },
>>     ++          { ignore_case ? "TENOR" : "tenor",
>>     ++            ignore_case ? "value4" : "value5" }
>>      +  };
>
> I suggested adding the following test case:
>
>                { ignore_case ? "FOOBarFrotZ" : "foobarfrotz",
>                  ignore_case ? : "value3" : "value4" }
>
> to better check that things work well especially when not ignoring the case.
>
> This is because, when not ignoring the case, there used to be a choice
> between { "fooBarFrotz", "value3" } and { "foobarfrotz", "value4" }
> that can be decided only by the case of the key in 'query'. But
> instead you removed that choice from 'key_val'.
>
> And it seems to me that the new test case you added doesn't bring much value.
>
> Maybe there was something wrong in what I suggested, but then please explain it.
>
> The other changes look good to me and seem to address the suggestions
> made by others and me.
>
> Thanks!

Thanks for a careful review, and of course thanks for working on the
patch, A U Thor ;-)

  reply	other threads:[~2024-07-31 18:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-28 12:41 [GSoC][PATCH] t: port helper/test-hashmap.c to unit-tests/t-hashmap.c Ghanshyam Thakkar
2024-07-08 16:15 ` [GSoC][PATCH v2] " Ghanshyam Thakkar
2024-07-09 19:34   ` Josh Steadmon
2024-07-09 21:42     ` Junio C Hamano
2024-07-10 19:41       ` Ghanshyam Thakkar
2024-07-09 23:27     ` Ghanshyam Thakkar
2024-07-10 10:19     ` Phillip Wood
2024-07-11 18:54       ` Ghanshyam Thakkar
2024-07-11 23:51   ` [GSoC][PATCH v3] " Ghanshyam Thakkar
2024-07-12  0:00     ` Ghanshyam Thakkar
2024-07-12 17:14       ` Junio C Hamano
2024-07-25 12:48     ` Christian Couder
2024-07-30 11:50     ` [PATCH v4] " A U Thor
2024-07-31 17:18       ` Christian Couder
2024-07-31 18:50         ` Junio C Hamano [this message]
2024-08-02  2:28         ` Ghanshyam Thakkar
2024-08-03 13:34       ` [GSoC][PATCH v5] " Ghanshyam Thakkar
2024-08-07 14:33         ` Christian Couder
2024-08-07 14:44           ` Ghanshyam Thakkar
2024-08-07 16:20           ` Junio C Hamano

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq7cd12y5r.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=chriscool@tuxfamily.org \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kaartic.sivaraam@gmail.com \
    --cc=phillip.wood123@gmail.com \
    --cc=shyamthakkar001@gmail.com \
    --cc=steadmon@google.com \
    /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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.