public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "email at miropalmu dot cc" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/115339] New: Missing -Wpedantic warning for a declarative nested-name-specifier with a decltype-specifier.
Date: Tue, 04 Jun 2024 07:31:07 +0000	[thread overview]
Message-ID: <bug-115339-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 115339
           Summary: Missing -Wpedantic warning for a declarative
                    nested-name-specifier with a decltype-specifier.
           Product: gcc
           Version: 15.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: email at miropalmu dot cc
  Target Milestone: ---

Following compiles on a GCC 15.0.0 20240604 without warnings with flags
-std=c++26 -Wall -Wextra -Wpedantic (https://godbolt.org/z/6fdbo9YcW):

```
struct X {
    struct a;
};
auto x = X{};
struct decltype(x)::a{};
```

However it should be ill-formed or at least give warning with -Wpedantic,
as [expr.prim.id.general] states (https://eel.is/c++draft/expr.prim.id#qual-2):

> A declarative nested-name-specifier shall not have a decltype-specifier.

`decltype(x)` is declarative nested-name-specifier as it is part of
class-head-name.

             reply	other threads:[~2024-06-04  7:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04  7:31 email at miropalmu dot cc [this message]
2024-06-04 15:57 ` [Bug c++/115339] " mpolacek 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-115339-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).