public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "andreas.milton.m at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/46061] New: Variadic Template Templates: not expandable into fixed-size argument list, Implementation Gap. Date: Mon, 18 Oct 2010 01:14:00 -0000 [thread overview] Message-ID: <bug-46061-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46061 Summary: Variadic Template Templates: not expandable into fixed-size argument list, Implementation Gap. Product: gcc Version: 4.5.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: andreas.milton.m@gmail.com Created attachment 22073 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22073 full demo for bug ( .ii-file <14 lines) The following struct "type_list" marks a list of types, which is constructed as a template template class with a variadic type list of template arguments: template <typename H, template <typename> class T, template <typename> class... R> struct type_list { typedef type_list< T<H>, R... > tail; }; template<typename H, template<typename> class T> struct type_list<H,T> {}; The code (attached as variadic_templ_templ.ii) produces the following error-message (identical for gcc 4.4 and 4.5.1): "sorry, unimplemented: cannot expand ‘template<class> class ... R ...’ into a fixed-length argument list" No other flags than -v -save-temps -Wall -std=c++0x were used.
next reply other threads:[~2010-10-18 1:14 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-18 1:14 andreas.milton.m at gmail dot com [this message] 2010-10-18 12:07 ` [Bug c++/46061] [C++0x] " redi 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-46061-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).