From: Jason Merrill <jason@redhat.com>
To: Patrick Palka <ppalka@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH v2 1/3] c++: sort candidates according to viability
Date: Tue, 24 Oct 2023 17:28:29 -0400 [thread overview]
Message-ID: <924c1ea5-c789-4820-85f3-2ce8c73188bf@redhat.com> (raw)
In-Reply-To: <20231023235154.2971561-1-ppalka@redhat.com>
On 10/23/23 19:51, Patrick Palka wrote:
> The second patch in this series is new and ensures that the candidates
> list isn't mysteriously missing some candidates when noting other
> candidates due to deletedness.
>
> -- >8 --
>
> This patch:
>
> * changes splice_viable to move the non-viable candidates to the end
> of the list instead of removing them outright
Please consistently spell this "non-viable" rather than "unviable".
> +tourney (struct z_candidate *&candidates, tsubst_flags_t complain)
> {
> struct z_candidate *champ = candidates, *challenger;
> int fate;
> struct z_candidate *champ_compared_to_predecessor = nullptr;
> + struct z_candidate *champ_predecessor = nullptr;
> + struct z_candidate *challenger_predecessor = champ;
Rather than adding two more variables to keep synchronized, maybe we
want champ and challenger to be **, like the tail variables in
splice_viable?
Jason
prev parent reply other threads:[~2023-10-24 21:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 23:51 Patrick Palka
2023-10-23 23:51 ` [PATCH v2 2/3] c++: remember candidates that we ignored Patrick Palka
2023-10-24 21:51 ` Jason Merrill
2023-10-23 23:51 ` [PATCH v2 3/3] c++: note other candidates when diagnosing deletedness Patrick Palka
2023-10-24 21:56 ` Jason Merrill
2023-10-24 21:28 ` Jason Merrill [this message]
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=924c1ea5-c789-4820-85f3-2ce8c73188bf@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ppalka@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).