public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99992] Diagnose C++11 constexpr body that isn't just return even in uninstantiated templates
Date: Fri, 09 Apr 2021 13:47:28 +0000	[thread overview]
Message-ID: <bug-99992-4-Ah2kfJycah@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99992-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
C++11 says:
"its function-body shall be = delete, = default, or a compound-statement that
contains only
— null statements,
— static_assert-declarations
— typedef declarations and alias-declarations that do not define classes or
enumerations,
— using-declarations,
— using-directives,
— and exactly one return statement;"
so perhaps if we on a constexpr function template see anything other than the
above ones, even if it e.g. could be some statement that is using some
parameter pack that would for empty pack instantiate to nothing, we could
diagnose it?

  reply	other threads:[~2021-04-09 13:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09 11:42 [Bug c++/99992] New: " jakub at gcc dot gnu.org
2021-04-09 13:47 ` jakub at gcc dot gnu.org [this message]
2021-04-09 13:54 ` [Bug c++/99992] " jakub at gcc dot gnu.org
2021-04-09 16:42 ` redi at gcc dot gnu.org
2021-08-28 21:49 ` 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-99992-4-Ah2kfJycah@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).