public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "metaprogrammingtheworld at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/52757] New: [C++11] A lamba functions is not able to be used as a function pointer when passed as an explicit template argument Date: Wed, 28 Mar 2012 19:59:00 -0000 [thread overview] Message-ID: <bug-52757-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52757 Bug #: 52757 Summary: [C++11] A lamba functions is not able to be used as a function pointer when passed as an explicit template argument Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: metaprogrammingtheworld@gmail.com The following are two simple test-cases for what appears to be the same problem. The main issue is that you can't use a lambda function as a template argument where the template parameter type is a function pointer type. It seems that this happens because there is no constexpr conversion operator from the lambda function type to the corresponding function pointer type (in places where the pointer is not required to be a compile-time constant, the conversion works properly, as expected). First test-case: ////////// template< int (*)() > struct foo; typedef foo< [] { return 0; } > bar; ////////// main.cpp:2:31: error: could not convert template argument '{}' to 'int (*)()' main.cpp:2:36: error: invalid type in declaration before ';' token Second test-case (error message may shed light on the root of the problem): ////////// constexpr int (*foo)() = [] { return 0; }; ////////// main.cpp:1:41: error: '<lambda()>::operator int (*)()() const' is not a constexpr function
next reply other threads:[~2012-03-28 19:51 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-28 19:59 metaprogrammingtheworld at gmail dot com [this message] 2012-03-28 20:10 ` [Bug c++/52757] " redi at gcc dot gnu.org 2012-03-28 20:13 ` metaprogrammingtheworld at gmail dot com 2012-03-28 20:45 ` 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-52757-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).