public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/20906] [C++98/C++11/c++14 only] excessive diagnostic messages for missing template arguments Date: Thu, 16 Dec 2021 22:39:52 +0000 [thread overview] Message-ID: <bug-20906-4-8BE3CF1Isn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-20906-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=20906 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|excessive diagnostic |[C++98/C++11/c++14 only] |messages for missing |excessive diagnostic |template arguments |messages for missing | |template arguments --- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Hmm, using -std=c++17 (the default now) and -std=c++20 we get: <source>:4:34: error: class template placeholder 'bar' not permitted in this context 4 | template<int k> void foo<k>::pop(bar&, int) {} | ^~~ <source>:4:34: note: use 'auto' for an abbreviated function template <source>:4:22: error: no declaration matches 'void foo<i>::pop(...)' 4 | template<int k> void foo<k>::pop(bar&, int) {} | ^~~~~~ <source>:3:35: note: candidate is: 'void foo<i>::pop(bar<i>&, int)' 3 | template<int i> struct foo { void pop(bar<i>& b, int j); }; | ^~~ <source>:3:24: note: 'struct foo<i>' defined here 3 | template<int i> struct foo { void pop(bar<i>& b, int j); }; | ^~~ Which I suspect is decent really.
prev parent reply other threads:[~2021-12-16 22:39 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-20906-4@http.gcc.gnu.org/bugzilla/> 2021-12-16 22:37 ` [Bug c++/20906] " pinskia at gcc dot gnu.org 2021-12-16 22:39 ` pinskia 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-20906-4-8BE3CF1Isn@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).