public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/52757] [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 20:10:00 -0000	[thread overview]
Message-ID: <bug-52757-4-EDJ1TgPHKa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52757-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52757

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-03-28 19:58:41 UTC ---
(In reply to comment #0)
> that this happens because there is no constexpr conversion operator from the
> lambda function type to the corresponding function pointer type 

Is there supposed to be?

"The closure type for a lambda-expression with no lambda-capture has a public
non-virtual non-explicit const conversion function to pointer to function
having the same parameter and return types as the closure type's function call
operator. The value returned by this conversion function shall be the address
of a function that, when invoked, has the same effect as invoking the closure
type's function call operator."

A closure is not literal and its conversion operator isn't constexpr.


  reply	other threads:[~2012-03-28 19:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-28 19:59 [Bug c++/52757] New: " metaprogrammingtheworld at gmail dot com
2012-03-28 20:10 ` redi at gcc dot gnu.org [this message]
2012-03-28 20:13 ` [Bug c++/52757] " 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-EDJ1TgPHKa@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).