public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "herring at lanl dot gov" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/104577] needs copy constructor for class non-type template parameter
Date: Sat, 11 Feb 2023 04:35:47 +0000 [thread overview]
Message-ID: <bug-104577-4-gdoeeywK4k@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104577-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104577
S. Davis Herring <herring at lanl dot gov> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |herring at lanl dot gov
--- Comment #4 from S. Davis Herring <herring at lanl dot gov> ---
The understood direction for CWG2459 makes it clear that class-type template
parameters must indeed be copied; in fact, they have to be copied twice in some
cases to guarantee that they have the correct value when user-provided
constructors are involved.
next prev parent reply other threads:[~2023-02-11 4:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 3:55 [Bug c++/104577] New: needs copy constructor to call method of " f.heckenbach@fh-soft.de
2022-02-18 1:14 ` [Bug c++/104577] needs copy constructor for " pinskia at gcc dot gnu.org
2022-12-26 4:19 ` mail at jhellings dot nl
2022-12-28 1:30 ` f.heckenbach@fh-soft.de
2023-02-11 4:35 ` herring at lanl dot gov [this message]
2023-06-05 19:29 ` ppalka 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-104577-4-gdoeeywK4k@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).