From: Patrick Steinhardt <ps@pks.im>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH] refs: forbid clang to complain about unreachable code
Date: Sat, 11 Oct 2025 12:49:30 +0200 [thread overview]
Message-ID: <aOo2Os8Q0X3WaLM0@pks.im> (raw)
In-Reply-To: <2346bcc7-b60e-0ad6-14fe-c0b49e427921@gmx.de>
On Fri, Oct 10, 2025 at 03:49:37PM +0200, Johannes Schindelin wrote:
> Hi Patrick,
>
> On Fri, 10 Oct 2025, Patrick Steinhardt wrote:
>
> > diff --git a/refs/files-backend.c b/refs/files-backend.c
> > index bb2bec3807..cb402a2a54 100644
> > --- a/refs/files-backend.c
> > +++ b/refs/files-backend.c
> > @@ -2115,7 +2115,7 @@ static int commit_ref_update(struct files_ref_store *refs,
> > }
> >
> > #ifdef NO_SYMLINK_HEAD
> > -#define create_ref_symlink(a, b) (-1)
> > +#define create_ref_symlink(a, b) NOT_CONSTANT(-1)
> > #else
> > static int create_ref_symlink(struct ref_lock *lock, const char *target)
> > {
>
> While this is correct, and "closer to the root", in my experience it is
> better to have work-arounds closer to where the symptom appears. In this
> case, it would be directly in the condition of the `if ()` construct.
> Therefore, I would prefer to keep the proposed patch as-is.
As said, I don't feel strongly about it, so this is totally fine with
me. Thanks!
Patrick
next prev parent reply other threads:[~2025-10-11 10:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 7:46 [PATCH] refs: forbid clang to complain about unreachable code Johannes Schindelin via GitGitGadget
2025-10-09 20:30 ` Junio C Hamano
2025-10-10 5:36 ` Patrick Steinhardt
2025-10-10 5:34 ` Patrick Steinhardt
2025-10-10 13:49 ` Johannes Schindelin
2025-10-11 10:49 ` Patrick Steinhardt [this message]
2025-10-10 15:48 ` 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=aOo2Os8Q0X3WaLM0@pks.im \
--to=ps@pks.im \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.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 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 NNTP newsgroup(s).