From: shejialuo <shejialuo@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/4] string-list: allow passing NULL for `get_entry_index`
Date: Mon, 15 Sep 2025 20:08:10 +0800 [thread overview]
Message-ID: <aMgBqnwKSKDC5g0I@ArchLinux> (raw)
In-Reply-To: <xmqq5xdsyjoz.fsf@gitster.g>
On Mon, Sep 08, 2025 at 09:48:12AM -0700, Junio C Hamano wrote:
> shejialuo <shejialuo@gmail.com> writes:
>
> > Callers of `get_entry_index()` are required to pass a non-NULL
> > `exact_match` parameter to receive information about whether an exact
> > match is found. However, in some cases, callers only need the index
> > position.
> >
> > Let's allow callers to pass NULL for the `exact_match` parameter
> > when they don't need this information, reducing unnecessary variable
> > declarations in calling code.
> >
> > Signed-off-by: shejialuo <shejialuo@gmail.com>
> > ---
> > string-list.c | 6 ++++--
> > 1 file changed, 4 insertions(+), 2 deletions(-)
>
> I do not quite see the point of adding these conditional assignments
> to clutter the control flow. What benefit do these callers gain by
> not having to have a throw-away int variable on the stack and
> passing its address to the call chain?
>
I want to make the commit small. However, I have introduced confusion to
the reviewers. I would rebase the first commit and second commit into
one commit to improve this.
Thanks,
Jialuo
next prev parent reply other threads:[~2025-09-15 12:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-07 16:40 [PATCH 1/4] string-list: allow passing NULL for `get_entry_index` shejialuo
2025-09-08 16:48 ` Junio C Hamano
2025-09-10 0:09 ` Ben Knoble
2025-09-10 1:32 ` Junio C Hamano
2025-09-10 2:04 ` Ben Knoble
2025-09-15 12:08 ` shejialuo [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-07 16:40 [PATCH 0/4] enhance string-list API to fix sign compare warnings shejialuo
2025-09-07 16:42 ` [PATCH 1/4] string-list: allow passing NULL for `get_entry_index` shejialuo
2025-09-09 6:22 ` Patrick Steinhardt
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=aMgBqnwKSKDC5g0I@ArchLinux \
--to=shejialuo@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.