public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/99213] New: Incorrect pretty printing of local class type when type's context contains a class template specialization Date: Tue, 23 Feb 2021 03:39:26 +0000 [thread overview] Message-ID: <bug-99213-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99213 Bug ID: 99213 Summary: Incorrect pretty printing of local class type when type's context contains a class template specialization Product: gcc Version: 10.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: ppalka at gcc dot gnu.org Target Milestone: --- Consider: template <class T> struct A { template <class U> static auto f() { struct S{}; return S{}; } }; using type = void; using type = decltype(A<int>::f<char>()); // A<int>::f<char>()::S For this testcase, GCC 10/11 outputs: <source>:11:7: error: conflicting declaration 'using type = struct A<T>::f<char>::S' 11 | using type = decltype(A<int>::f<char>()); | ^~~~ Note that the nested class type 'S' gets pretty printed as 'A<T>::f<char>::S', i.e. the argument for the template parameter T is missing in the nested-name-specifier. GCC 9 outputs: <source>:11:7: error: conflicting declaration 'using type = struct A<T>::f() [with U = char; T = int]::S' 11 | using type = decltype(A<int>::f<char>()); | ^~~~ Which isn't perfect either, but importantly all template arguments are shown in the type.
next reply other threads:[~2021-02-23 3:39 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-23 3:39 ppalka at gcc dot gnu.org [this message] 2021-02-23 3:46 ` [Bug c++/99213] " ppalka at gcc dot gnu.org 2021-02-25 21:45 ` [Bug c++/99213] Suboptimal " cvs-commit at gcc dot gnu.org 2021-02-25 21:46 ` ppalka at gcc dot gnu.org
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-99213-4@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: linkBe 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).