public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "richard-gccbugzilla at metafoo dot co.uk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/59673] New: wrong specialization used when a partial specialization of a member template is explicitly specialized Date: Sat, 04 Jan 2014 02:22:00 -0000 [thread overview] Message-ID: <bug-59673-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59673 Bug ID: 59673 Summary: wrong specialization used when a partial specialization of a member template is explicitly specialized Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: richard-gccbugzilla at metafoo dot co.uk GCC rejects this: template<typename A> struct X { template<typename B> struct Y; template<typename B> struct Y<B[1]> { int x; }; // #1 template<typename B> struct Y<B[2]> { int y; }; }; template<> template<typename B> struct X<int>::Y<B[1]> { int z; }; // #2 int a = X<int>::Y<int[1]>().z; ... because it uses #1, not #2, when instantiating X<int>::Y<int[1]>.
next reply other threads:[~2014-01-04 2:22 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-04 2:22 richard-gccbugzilla at metafoo dot co.uk [this message] 2015-03-18 20:16 ` [Bug c++/59673] " paolo.carlini at oracle dot com 2020-04-14 23:41 ` dacamara.cameron 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-59673-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).