public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ghartshaw at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/58743] New: [C++11] parameter packs not expanded with '...' Date: Wed, 16 Oct 2013 03:54:00 -0000 [thread overview] Message-ID: <bug-58743-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58743 Bug ID: 58743 Summary: [C++11] parameter packs not expanded with '...' Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: ghartshaw at gmail dot com Created attachment 31015 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31015&action=edit Compiliation error messages. The following test case gives an "parameter packs not expanded with '...'" error where it should not: $ cat error_example.cpp struct tensor { constexpr tensor( int value ) : _value( value ) {} template <int... Indices> constexpr int value() const { return _value; } private: int _value; }; template <typename T> struct printer { static int get( T const & tensor ) { return detail<>::get( tensor ); } private: template <int... Indices> struct detail { static int get( T const & tensor ) { return tensor.value<Indices...>(); } }; }; int main() { printer<tensor>::get( tensor<int>(1) ); } $ g++-4.9 --version g++-4.9 (GCC) 4.9.0 20131015 (experimental) $ g++-4.9 -std=c++11 -Wall -Wextra error_example.cpp -save-temps -v 2>output.txt
next reply other threads:[~2013-10-16 3:54 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-10-16 3:54 ghartshaw at gmail dot com [this message] 2013-10-16 8:55 ` [Bug c++/58743] " paolo.carlini at oracle dot com 2013-10-16 21:39 ` paolo.carlini at oracle 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-58743-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).