public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "daniel.kruegler at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/51203] [C++0x] Recursive alias template specialization causes compiler segfault
Date: Fri, 18 Nov 2011 19:17:00 -0000 [thread overview]
Message-ID: <bug-51203-4-2dAHRiVZ6A@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51203-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51203
Daniel Krügler <daniel.kruegler at googlemail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |daniel.kruegler at
| |googlemail dot com
--- Comment #2 from Daniel Krügler <daniel.kruegler at googlemail dot com> 2011-11-18 19:03:14 UTC ---
(In reply to comment #1)
> template <typename t>
> struct foo {
> template <int n>
> using next = typename foo<t>::next<n + 1>;
> template <>
> using next<10> = int; // not sure if alias templates can be specialized
> };
Alias templates cannot be specialized, this is by design.
next prev parent reply other threads:[~2011-11-18 19:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 7:49 [Bug c++/51203] New: Recursive alias templates not working pubby.8 at gmail dot com
2011-11-18 8:22 ` [Bug c++/51203] " pubby.8 at gmail dot com
2011-11-18 8:27 ` [Bug c++/51203] Recursive alias template specialization causes compiler segfault pubby.8 at gmail dot com
2011-11-18 19:17 ` daniel.kruegler at googlemail dot com [this message]
2011-11-25 13:28 ` [Bug c++/51203] [C++0x] " dodji 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-51203-4-2dAHRiVZ6A@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: link
Be 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).