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++/50431] [C++0x] bug in def array size with a lambda
Date: Fri, 16 Sep 2011 14:01:00 -0000 [thread overview]
Message-ID: <bug-50431-4-VlJLe6rNzh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50431-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50431
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-09-16 13:47:49 UTC ---
(In reply to comment #2)
> BUG1:
> auto sz = []()->constexpr long { return 100L; };
> int arr[sz()];
>
> Why constexpr for lambda won't be compiled? Can i not use auto type for a
> lambda variant?
The closure type's function call operator can be const but not constexpr.
You can use auto for a lambda, you just can't have a constexpr lambda.
Why do you want it to work?
What advantage is there to using a lambda instead of named function? e.g.
constexpr long sz() { return 100L; };
int arr[sz()];
next prev parent reply other threads:[~2011-09-16 13:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 11:41 [Bug c++/50431] New: lambda bug for array size def zhudiqi at 163 dot com
2011-09-16 11:51 ` [Bug c++/50431] " zhudiqi at 163 dot com
2011-09-16 12:05 ` zhudiqi at 163 dot com
2011-09-16 12:45 ` [Bug c++/50431] [C++0x] bug in def array size with a lambda redi at gcc dot gnu.org
2011-09-16 14:01 ` redi at gcc dot gnu.org [this message]
2011-11-05 21:33 ` paolo.carlini at oracle dot com
2011-11-13 13:09 ` zhudiqi at 163 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-50431-4-VlJLe6rNzh@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).