public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/101883] class template argument deduction in non-type template parameter allows explicit deduction guide
Date: Wed, 06 Oct 2021 14:15:15 +0000	[thread overview]
Message-ID: <bug-101883-4-2z1188vTT6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101883-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Patrick Palka
<ppalka@gcc.gnu.org>:

https://gcc.gnu.org/g:52dd840c5eba25ef54dee3f1c78f371032a7c051

commit r11-9078-g52dd840c5eba25ef54dee3f1c78f371032a7c051
Author: Patrick Palka <ppalka@redhat.com>
Date:   Wed Aug 18 08:37:42 2021 -0400

    c++: ignore explicit dguides during NTTP CTAD [PR101883]

    Since (template) argument passing is a copy-initialization context,
    we mustn't consider explicit deduction guides when deducing a CTAD
    placeholder type of an NTTP.

            PR c++/101883

    gcc/cp/ChangeLog:

            * pt.c (convert_template_argument): Pass LOOKUP_IMPLICIT to
            do_auto_deduction.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp2a/nontype-class49.C: New test.

    (cherry picked from commit a6b3db3e8625a3cba1240f0b5e1a29bd6c68b8ca)

  parent reply	other threads:[~2021-10-06 14:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-12 15:29 [Bug c++/101883] New: " barry.revzin at gmail dot com
2021-08-12 18:04 ` [Bug c++/101883] " ppalka at gcc dot gnu.org
2021-08-18 12:39 ` cvs-commit at gcc dot gnu.org
2021-10-06 14:15 ` cvs-commit at gcc dot gnu.org [this message]
2021-10-06 14:16 ` 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-101883-4-2z1188vTT6@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).