public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "potswa at mac dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/52809] New: Template non-dependent static_assert diagnostics may confuse
Date: Sat, 31 Mar 2012 16:55:00 -0000	[thread overview]
Message-ID: <bug-52809-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 52809
           Summary: Template non-dependent static_assert diagnostics may
                    confuse
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: potswa@mac.com


A static_assert declaration that does not depend on template parameters will be
detected and reported while parsing the template, before any instantiation.
This is OK because such a template would have no valid instantiation, which
immediately renders the program ill-formed.

In terms of cosmetic QOI, however, it would be better to clarify the messages
for users who don't know all the rules. Intuitively, the assertion shouldn't be
evaluated until instantiation, regardless of dependence. The user might expect
an uninstantiated template to pass through. We should add something like
"error: template MyTemplate cannot have a valid instantiation" after the
static_assert diagnostic.

Example code and result, as currently implemented:

template< bool b >
struct s {
    static_assert( b, "uhoh" );
    static_assert( false, "yikes" );
};

s< false > q;

depassert.cpp:4:1: error: static assertion failed: yikes
depassert.cpp: In instantiation of ‘struct s<false>’:
depassert.cpp:7:12:   required from here
depassert.cpp:3:1: error: static assertion failed: uhoh


             reply	other threads:[~2012-03-31 16:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-31 16:55 potswa at mac dot com [this message]
2012-03-31 16:58 ` [Bug c++/52809] " paolo.carlini at oracle dot com
2021-08-04  6:29 ` pinskia at gcc dot gnu.org
2023-02-18 21:19 ` cvs-commit 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-52809-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).