public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86439] CTAD with deleted copy constructor fails due to deduction-guide taking by value
Date: Tue, 22 Jun 2021 14:25:18 +0000	[thread overview]
Message-ID: <bug-86439-4-NkjBoRYVqm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-86439-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Patrick Palka <ppalka at gcc dot gnu.org> ---
Another side effect of this is that GCC incorrectly rejects the following use
of CTAD + braced-init-lists:

struct B { };
struct C { };

template<class T>
struct A {
  A(T, B);
};

template<class T>
A(T, C) -> A<T>;

A a(0, {});

The problem is that building the call to the deduction guide has the side
effect of changing the type of the {} to C, which causes later overload
resolution to fail because C isn't convertible to B.

  parent reply	other threads:[~2021-06-22 14:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-86439-4@http.gcc.gnu.org/bugzilla/>
2021-06-21 12:56 ` ppalka at gcc dot gnu.org
2021-06-22 14:25 ` ppalka at gcc dot gnu.org [this message]
2021-06-23 12:25 ` cvs-commit at gcc dot gnu.org
2021-07-09 19:34 ` ppalka at gcc dot gnu.org
2021-09-01 14:13 ` 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-86439-4-NkjBoRYVqm@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).