public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "johelegp at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99501] New: Can't forward declare partial specialization of template with NTTP previously partially specialized
Date: Wed, 10 Mar 2021 00:55:32 +0000	[thread overview]
Message-ID: <bug-99501-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 99501
           Summary: Can't forward declare partial specialization of
                    template with NTTP previously partially specialized
           Product: gcc
           Version: 11.0
               URL: https://godbolt.org/z/Mhnxrf
            Status: UNCONFIRMED
          Keywords: rejects-valid
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: johelegp at gmail dot com
                CC: johelegp at gmail dot com
  Target Milestone: ---

See https://godbolt.org/z/Mhnxrf.
```C++
template<auto>struct X;
template<auto V>requires requires{V.a;}struct X<V>;
template<auto V>requires requires{V.b;}struct X<V>;
```
Completed:
```C++
template<auto>struct X{};
template<auto V>requires requires{V.a;}struct X<V>{static constexpr bool
v{false};};
template<auto V>requires requires{V.b;}struct X<V>;
struct A{int a;};
static_assert(!X<A{}>::v);
struct B{int b;};
template<auto V>requires requires{V.b;}struct X<V>{static constexpr bool
v{true};};
static_assert(X<B{}>::v);
```

             reply	other threads:[~2021-03-10  0:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10  0:55 johelegp at gmail dot com [this message]
2022-05-24 16:53 ` [Bug c++/99501] " 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-99501-4@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).