public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "barry.revzin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/106596] New: Not a helpful diagnostic when putting things out of order in a member function
Date: Fri, 12 Aug 2022 13:12:17 +0000	[thread overview]
Message-ID: <bug-106596-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 106596
           Summary: Not a helpful diagnostic when putting things out of
                    order in a member function
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: barry.revzin at gmail dot com
  Target Milestone: ---

Consider this example:

template <class T> concept C = true;

template <class T>
struct Widget {
    void foo() requires C<T> noexcept;  
};

The issue here is that the noexcept needs to go before the requires clause, but
how many people really remember what the order of these things needs to be?

The gcc 12.1 error for this is:

<source>:5:25: error: expected ';' at end of member declaration
    5 |     void foo() requires C<T> noexcept;
      |                         ^~~~
      |                             ;
<source>:5:30: error: expected unqualified-id before 'noexcept'
    5 |     void foo() requires C<T> noexcept;
      |                              ^~~~~~~~

I suspect this might be a difficult thing to provide a diagnostic for, but this
particular one is pretty unhelpful. The first one is suggesting I needed to
write void foo() requires; which isn't even valid.

Hypothetical ideal:

<source>:5:30: error: the noexcept-specifier needs to precede the
requires-clause
    5 |     void foo() requires C<T> noexcept;
      |                ^~~~~~~~~~~~~ ^~~~~~~~
      |                noexcept requires C<T>;

             reply	other threads:[~2022-08-12 13:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-12 13:12 barry.revzin at gmail dot com [this message]
2022-08-12 13:23 ` [Bug c++/106596] " 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-106596-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).