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++/67594] Bug on partial specialization? Incomplete type. Date: Tue, 15 Sep 2015 23:27:00 -0000 [thread overview] Message-ID: <bug-67594-4-zWkr0AHbaP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67594-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67594 --- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> --- The primary template defines the default argument for the second parameter. The C<float,I> partial specialization is irrelevant, it isn't used. The C<float> specialization is identical to C<float, 1> because it uses the default argument, so if you write it like that then it should be obvious the code is wrong: template <typename B, int I=1> class C{}; template <int I> class C<float,I>{}; // unused template <> class C<float, 1> : public C<float, 1> {}; ^^^^^^^^^^^ ^^^^^^^^^^^ The base class matches the C<float, 1> specialization not the C<float, I> partial specialization because C<float, 1> is more specialized. So the base class is the same type, and of course a type cannot derive from itself.
next prev parent reply other threads:[~2015-09-15 23:27 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-09-15 22:00 [Bug c++/67594] New: " vincent.lextrait at gmail dot com 2015-09-15 22:23 ` [Bug c++/67594] " vincent.lextrait at gmail dot com 2015-09-15 23:00 ` redi at gcc dot gnu.org 2015-09-15 23:02 ` vincent.lextrait at gmail dot com 2015-09-15 23:27 ` redi at gcc dot gnu.org [this message] 2015-09-15 23:35 ` vincent.lextrait at gmail dot com
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-67594-4-zWkr0AHbaP@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).