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++/54948] template unnecessarily displayed as "A< template-parameter-1-1 >" not "A<T>" Date: Tue, 18 Jan 2022 13:24:12 +0000 [thread overview] Message-ID: <bug-54948-4-AO6OxtuiXN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54948-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54948 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=104094 --- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> --- This continues to be annoying. Libstdc++ has loads of forward declarations of templates, e.g. in <type_traits>: // Forward declarations template<typename> struct is_reference; template<typename> struct is_function; template<typename> struct is_void; template<typename> struct remove_cv; template<typename> struct is_const; Which means we then get diagnostics containing: std::is_same<_U1, typename std::remove_cv< <template-parameter-1-1> >::type&> I agree with Manu that this could just show "typename" here. We don't refer to the template-parameter-1-1 type again in the diagnostic, so why do we care about uniquely identifying it as 1-1? But why is it even using the name from the remove_cv declaration? That should not be appearing in the *use* of remove_cv here. I've filed that as PR 104094.
prev parent reply other threads:[~2022-01-18 13:24 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-17 13:25 [Bug c++/54948] New: " redi at gcc dot gnu.org 2013-04-20 12:03 ` [Bug c++/54948] " manu at gcc dot gnu.org 2022-01-18 13:24 ` redi at gcc dot gnu.org [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=bug-54948-4-AO6OxtuiXN@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).