public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/57012] pretty-printer does not handle well template parameter packs
Date: Tue, 10 Aug 2021 11:19:30 +0000 [thread overview]
Message-ID: <bug-57012-4-rpY7vXFMz3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57012-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57012
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
Last reconfirmed| |2021-08-10
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=54948
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
GCC improved error recovery with r219067 so that now it just prints one error:
gcc/testsuite/g++.dg/cpp0x/pr31432.C:2:10: error: parameter pack
‘<template-parameter-1-1>’ must be at the end of the template parameter list
2 | template<typename..., typename> struct A // { dg-error "parameter pack"
}
| ^~~~~~~~
Printing "<template-parameter-1-1>" is still not pretty.
See also PR 54948 and PR 101844.
If the template parameter (or template parameter pack) hasn't got a name, maybe
we should not try to print it. The caret location already shows which pack
we're talking about.
If it's unnamed, maybe special case the diagnostic so it just says "parameter
pack must be at the end ..." instead of making up a name which doesn't appear
in the source code.
parent reply other threads:[~2021-08-10 11:19 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-57012-4@http.gcc.gnu.org/bugzilla/>]
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=bug-57012-4-rpY7vXFMz3@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).