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++/106631] New: Unhelpful diagnostic on variable template specialization with unknown name
Date: Mon, 15 Aug 2022 21:24:43 +0000	[thread overview]
Message-ID: <bug-106631-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 106631
           Summary: Unhelpful diagnostic on variable template
                    specialization with unknown name
           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: ---

Short example:

template <class T>
constexpr bool trait = true;

template <>
constexpr bool triat<int> = false;

Note the typo on triat.

The current error message gcc provides is:

<source>:5:21: error: expected initializer before '<' token
    5 | constexpr bool triat<int> = false;
      |                     ^

Which is... technically true. Given that triat doesn't exist as a variable
template, the next thing coming up needs to be an initializer for it, since
this is really a declaration. But the intent was for it to specialize trait -
it seems like it's more likely that this kind of error would come from getting
the name of the variable template wrong rather than spelling the initializer
incorrectly?

So something like:

<source>:5:21: error: unknown variable template 'triat' being specialized
    5 | constexpr bool triat<int> = false;
      |                ^~~~~
    note: did you mean trait?

Would be much more helpful.

             reply	other threads:[~2022-08-15 21:24 UTC|newest]

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