From: Jason Merrill <jason@redhat.com>
To: Patrick Palka <ppalka@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH v3 3/3] c++: note other candidates when diagnosing deletedness
Date: Fri, 27 Oct 2023 18:29:28 -0400 [thread overview]
Message-ID: <35674d69-7c49-4b2d-99fb-977cf34e7e9a@redhat.com> (raw)
In-Reply-To: <20231027195532.2566822-3-ppalka@redhat.com>
On 10/27/23 15:55, Patrick Palka wrote:
> With the previous two patches in place, we can now extend our
> deletedness diagnostic to note the other considered candidates, e.g.:
>
> deleted16.C: In function 'int main()':
> deleted16.C:10:4: error: use of deleted function 'void f(int)'
> 10 | f(0);
> | ~^~~
> deleted16.C:5:6: note: declared here
> 5 | void f(int) = delete;
> | ^
> deleted16.C:5:6: note: candidate: 'void f(int)' (deleted)
> deleted16.C:6:6: note: candidate: 'void f(...)'
> 6 | void f(...);
> | ^
> deleted16.C:7:6: note: candidate: 'void f(int, int)'
> 7 | void f(int, int);
> | ^
> deleted16.C:7:6: note: candidate expects 2 arguments, 1 provided
>
> These notes are controlled by a new command line flag -fnote-all-cands,
> which also controls whether we note ignored candidates more generally.
>
> gcc/ChangeLog:
>
> * doc/invoke.texi (C++ Dialect Options): Document -fnote-all-cands.
>
> gcc/c-family/ChangeLog:
>
> * c.opt: Add -fnote-all-cands.
>
> gcc/cp/ChangeLog:
>
> * call.cc (print_z_candidates): Only print ignored candidates
> when -fnote-all-cands is set.
> (build_over_call): When diagnosing deletedness, call
> print_z_candidates if -fnote-all-cands is set.
My suggestion was also to suggest using the flag in cases where it would
make a difference, e.g.
note: some candidates omitted, use '-fnote-all-cands' to display them
Maybe "-fdiagnostics-all-candidates"?
Jason
next prev parent reply other threads:[~2023-10-27 22:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 19:55 [PATCH v3 1/3] c++: sort candidates according to viability Patrick Palka
2023-10-27 19:55 ` [PATCH v3 2/3] c++: remember candidates that we ignored Patrick Palka
2023-10-27 19:55 ` [PATCH v3 3/3] c++: note other candidates when diagnosing deletedness Patrick Palka
2023-10-27 22:29 ` Jason Merrill [this message]
2023-10-27 23:22 ` Patrick Palka
2023-10-27 23:28 ` Patrick Palka
2023-11-30 15:46 ` Patrick Palka
2023-12-10 19:32 ` Jason Merrill
2023-10-27 22:05 ` [PATCH v3 1/3] c++: sort candidates according to viability Jason Merrill
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=35674d69-7c49-4b2d-99fb-977cf34e7e9a@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).