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++/91798] Compiler rejects code due to template specialization of auto parameter value.
Date: Sat, 06 Apr 2024 02:45:24 +0000	[thread overview]
Message-ID: <bug-91798-4-28Jf6rr0eb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-91798-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |SUSPENDED

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
https://www.open-std.org/jtc1/sc22/wg21/docs/cwg_active.html#1647

And maybe others.

Note my other testcase was a full specialization rather than a partial.
Here is one with a partial which removes the variadic :
```
//Get type parameter at given index.
template<auto i, class T>
struct param
{
    static_assert(i > 0, "Index into parameter pack cannot be negative!");
    using type = typename param<i - 1, T>::type;
};

template<class T>
struct param<0, T>
{
    using type = T;
};

int main()
{
    typename param<0u, int>::type x = 'a';
    static_cast<void>(x);
}
```

Both GCC and EDG agree on this while clang and MSVC disagree. This is
definitely DR 1647 then. 

So suspended as the defect report is still active.

  parent reply	other threads:[~2024-04-06  2:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-91798-4@http.gcc.gnu.org/bugzilla/>
2021-03-08 10:12 ` redi at gcc dot gnu.org
2021-08-05  6:02 ` pinskia at gcc dot gnu.org
2024-04-06  2:37 ` pinskia at gcc dot gnu.org
2024-04-06  2:45 ` pinskia at gcc dot gnu.org [this message]
2024-04-06  2:46 ` pinskia 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-91798-4-28Jf6rr0eb@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).