From: Junio C Hamano <gitster@pobox.com>
To: Alex Henrie <alexhenrie24@gmail.com>
Cc: git@vger.kernel.org, cb@hashpling.org, dstolee@microsoft.com
Subject: Re: [PATCH v4] diffcore-break: use a goto instead of a redundant if statement
Date: Mon, 30 Sep 2019 10:36:39 +0900 [thread overview]
Message-ID: <xmqqa7amimzc.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20190929204322.1244907-1-alexhenrie24@gmail.com> (Alex Henrie's message of "Sun, 29 Sep 2019 14:43:22 -0600")
Alex Henrie <alexhenrie24@gmail.com> writes:
> The condition "if (q->nr <= j)" checks whether the loop exited normally
> or via a break statement. This check can be avoided by replacing the
> jump out of the inner loop with a jump to the end of the outer loop.
>
> With the break replaced by a goto, the two diff_q calls then can be
> replaced with a single diff_q call outside of the outer if statement.
I doubt that it is a good idea to do these two things. Especially I
do not see why the latter makes the resulting code better.
> Signed-off-by: Alex Henrie <alexhenrie24@gmail.com>
> ---
> diffcore-break.c | 14 ++++++--------
> 1 file changed, 6 insertions(+), 8 deletions(-)
>
> diff --git a/diffcore-break.c b/diffcore-break.c
> index 875aefd3fe..ee7519d959 100644
> --- a/diffcore-break.c
> +++ b/diffcore-break.c
> @@ -286,17 +286,15 @@ void diffcore_merge_broken(void)
> /* Peer survived. Merge them */
> merge_broken(p, pp, &outq);
> q->queue[j] = NULL;
> - break;
> + goto next;
> }
> }
> - if (q->nr <= j)
> - /* The peer did not survive, so we keep
> - * it in the output.
> - */
> - diff_q(&outq, p);
> + /* The peer did not survive, so we keep
> + * it in the output.
> + */
> }
> - else
> - diff_q(&outq, p);
> + diff_q(&outq, p);
> +next:;
> }
> free(q->queue);
> *q = outq;
next prev parent reply other threads:[~2019-09-30 1:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-29 20:43 [PATCH v4] diffcore-break: use a goto instead of a redundant if statement Alex Henrie
2019-09-30 1:36 ` Junio C Hamano [this message]
2019-09-30 7:45 ` Alex Henrie
2019-09-30 9:48 ` Junio C Hamano
2019-09-30 17:36 ` Alex Henrie
2019-10-02 5:55 ` 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=xmqqa7amimzc.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=alexhenrie24@gmail.com \
--cc=cb@hashpling.org \
--cc=dstolee@microsoft.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.
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).