public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <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: Fri, 18 Feb 2022 01:14:23 +0000	[thread overview]
Message-ID: <bug-104577-4-MfBvSlMTN4@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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2022-02-18
            Summary|needs copy constructor to   |needs copy constructor for
                   |call method of class        |class non-type template
                   |non-type template parameter |parameter
     Ever confirmed|0                           |1

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed, it is for more than just calling a method on the non-type template
argument even.
Here is testcase which shows that:
struct S
{
  constexpr S () = default;
  constexpr S (S &&) = delete;
  constexpr S (const S &) = delete;
};

template <S s> 
struct i
{
    int y = 1;
};

int main ()
{
  return i <S { }>{}.y;
}

  reply	other threads:[~2022-02-18  1:14 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 ` pinskia at gcc dot gnu.org [this message]
2022-12-26  4:19 ` [Bug c++/104577] needs copy constructor for " 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
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-MfBvSlMTN4@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).