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++/105841] [12/13 Regression] Change in behavior of CTAD for alias templates Date: Mon, 06 Jun 2022 12:50:42 +0000 [thread overview] Message-ID: <bug-105841-4-xYoTm4uszP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105841-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105841 Patrick Palka <ppalka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=103852 Known to work| |11.3.0 Known to fail| |12.1.0, 13.0 Last reconfirmed| |2022-06-06 CC| |jason at gcc dot gnu.org, | |ppalka at gcc dot gnu.org Target Milestone|--- |12.2 Summary|Change in behavior of CTAD |[12/13 Regression] Change |for alias templates |in behavior of CTAD for | |alias templates Status|UNCONFIRMED |NEW Keywords| |rejects-valid Ever confirmed|0 |1 --- Comment #1 from Patrick Palka <ppalka at gcc dot gnu.org> --- We started rejecting the testcase after r12-7984-ga11f204e5a30d1. Reduced rejects-valid example: template<class T, int N> struct A { A(...); }; template<class T, class... Ts> A(T, Ts...) -> A<T, sizeof...(Ts)>; template<class T, int N=0> using B = A<T, N>; B b(0, 0); Removing B's default template argument makes us accept again.
next prev parent reply other threads:[~2022-06-06 12:50 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-03 18:12 [Bug c++/105841] New: " avemilia at protonmail dot com 2022-06-06 12:50 ` ppalka at gcc dot gnu.org [this message] 2022-06-06 19:28 ` [Bug c++/105841] [12/13 Regression] " jason at gcc dot gnu.org 2022-06-06 20:12 ` jason at gcc dot gnu.org 2022-06-07 0:02 ` mike at spertus dot com 2022-06-07 4:05 ` jason at gcc dot gnu.org 2022-06-09 13:39 ` ppalka at gcc dot gnu.org 2022-07-25 16:11 ` rguenth at gcc dot gnu.org 2023-02-09 22:05 ` jason at gcc dot gnu.org 2023-02-09 23:07 ` jason at gcc dot gnu.org 2023-02-09 23:26 ` mike at spertus dot com 2023-02-10 16:29 ` mike at spertus dot com 2023-03-09 15:27 ` cvs-commit at gcc dot gnu.org 2023-03-09 15:27 ` cvs-commit at gcc dot gnu.org 2023-03-09 15:30 ` [Bug c++/105841] [12 " jason at gcc dot gnu.org 2023-05-08 12:24 ` rguenth at gcc dot gnu.org 2023-12-20 22:23 ` jason at gcc dot gnu.org 2024-04-17 12:22 ` hokein.wu at gmail dot com 2024-04-24 21:41 ` ppalka at gcc dot gnu.org 2024-04-25 10:31 ` hokein.wu at gmail dot com
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-105841-4-xYoTm4uszP@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: linkBe 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).