public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/110836] [C++20] g++ should report when there is no way to create structure or class
Date: Fri, 28 Jul 2023 08:20:31 +0000	[thread overview]
Message-ID: <bug-110836-4-abtQjP3WCP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110836-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Some classes are supposed to be impossible to create, e.g. the monostate
pattern where the class has static members and the whole API is in terms of
static members functions.

If you don't notice a class cannot be created until users compile your library
then you are missing some tests for that class. Why do you have a class that
has never been tested even once?

  parent reply	other threads:[~2023-07-28  8:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-28  6:08 [Bug c++/110836] New: " andris at gcc dot gnu.org
2023-07-28  6:20 ` [Bug c++/110836] [C++20] " pinskia at gcc dot gnu.org
2023-07-28  6:43 ` andris at gcc dot gnu.org
2023-07-28  8:20 ` redi at gcc dot gnu.org [this message]
2023-07-28  8:21 ` redi 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-110836-4-abtQjP3WCP@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).