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++/47959] New: [C++0x] brace-or-equal-initializer not allowed for static data member of const literal type
Date: Wed, 02 Mar 2011 17:34:00 -0000	[thread overview]
Message-ID: <bug-47959-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: [C++0x] brace-or-equal-initializer not allowed for
                    static data member of const literal type
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Keywords: rejects-valid
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: redi@gcc.gnu.org


struct Lit { constexpr Lit() {} };

struct L
{
    static const Lit l = Lit();
} ;

init.cc:5:30: error: 'constexpr' needed for in-class initialization of static
data member 'l' of non-integral type

I think the diagnostic is wrong.

[class.static.data] p3 says 

  If a static data member is of const literal type, its declaration in
  the class definition can specify a brace-or-equal-initializer in which
  every initializer-clause that is an assignment-expression is a constant
  expression.

Lit is a literal type, L::l is of const literal type, the initializer is a
constant expression, so the example should be accepted.


             reply	other threads:[~2011-03-02 17:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-02 17:34 redi at gcc dot gnu.org [this message]
2011-03-16 20:54 ` [Bug c++/47959] " jason 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-47959-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: 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).