public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fchelnokov at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/102367] New: Types may be defined in `decltype` or `sizeof` expressions in C++20
Date: Thu, 16 Sep 2021 14:48:44 +0000	[thread overview]
Message-ID: <bug-102367-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102367

            Bug ID: 102367
           Summary: Types may be defined in `decltype` or `sizeof`
                    expressions in C++20
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: fchelnokov at gmail dot com
  Target Milestone: ---

Since C++20 lambdas are allowed in not-evaluated context. So the code as
follows must be valid:
```
using T = decltype( []{ struct S{}; return S{}; }() );

[[maybe_unused]] constexpr auto N 
          = sizeof( []{ struct S{}; return S{}; }() );
```

It is indeed accepted by MSVC and Clang, but rejected by GCC, demo:
https://gcc.godbolt.org/z/jYjxcr1eP

The error is
```
error: types may not be defined in 'decltype' expressions
    1 | using T = decltype( []{ struct S{}; return S{}; }() );
      |                                 ^
<source>: In lambda function:
<source>:4:33: error: types may not be defined in 'sizeof' expressions
    4 |           = sizeof( []{ struct S{}; return S{}; }() );
      |             
```

             reply	other threads:[~2021-09-16 14:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-16 14:48 fchelnokov at gmail dot com [this message]
2021-09-16 18:41 ` [Bug c++/102367] types can be defined in lambdas in unevaluated expression (decltype/sizeof) " pinskia at gcc dot gnu.org
2021-10-12 23:40 ` pinskia 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-102367-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).