public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/104578] [12 Regression][CWG1315] accepts invalid partial  template specialization, non-type template argument depends on a template parameter
Date: Wed, 06 Apr 2022 14:44:32 +0000	[thread overview]
Message-ID: <bug-104578-4-XjrutabAiJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104578-4@http.gcc.gnu.org/bugzilla/>

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

Jason Merrill <jason at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[12 Regression] accepts     |[12 Regression][CWG1315]
                   |invalid partial  template   |accepts invalid partial
                   |specialization, non-type    |template specialization,
                   |template argument depends   |non-type template argument
                   |on a template parameter     |depends on a template
                   |                            |parameter
                 CC|                            |jason at gcc dot gnu.org,
                   |                            |ppalka at gcc dot gnu.org
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID

--- Comment #1 from Jason Merrill <jason at gcc dot gnu.org> ---
This was changed by r12-1093, which implements https://wg21.link/cwg1315 . 
This testcase seems like exactly the sort of thing that DR1315 intended to
allow.

      parent reply	other threads:[~2022-04-06 14:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-17  4:55 [Bug c++/104578] New: [12 Regression] " pinskia at gcc dot gnu.org
2022-02-17  5:01 ` [Bug c++/104578] " pinskia at gcc dot gnu.org
2022-04-06 14:44 ` jason at gcc dot gnu.org [this message]

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-104578-4-XjrutabAiJ@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).