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++/96840] New: Recursive substitution in constrained commutative operator
Date: Sat, 29 Aug 2020 00:29:34 +0000	[thread overview]
Message-ID: <bug-96840-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 96840
           Summary: Recursive substitution in constrained commutative
                    operator
           Product: gcc
           Version: 11.0
               URL: https://godbolt.org/z/cedacs
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: johelegp at gmail dot com
  Target Milestone: ---

I may be wrong, but I think this should compile. Clang accepts it as does GCC
10.2 and did the GCC 11 build from a little while ago.
See the URL:
```C++
template <class T, class U> concept C = requires(T t, U u) { t * u; };
template <class Rep> struct Int {
     template <class T> requires C<T, Rep> friend void operator*(T, Int) { }
     template <class T> requires C<T, Rep> friend void operator*(Int, T) { }
};
void f() { 0 * Int<int>{}; }
```

             reply	other threads:[~2020-08-29  0:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-29  0:29 johelegp at gmail dot com [this message]
2020-08-31  6:31 ` [Bug c++/96840] [11 Regression] " rguenth at gcc dot gnu.org
2020-09-28 15:33 ` ppalka at gcc dot gnu.org
2020-10-16 12:05 ` rguenth at gcc dot gnu.org
2020-12-18  3:36 ` cvs-commit at gcc dot gnu.org
2021-02-01 17:58 ` ppalka at gcc dot gnu.org
2021-12-30 14:06 ` johelegp at gmail dot com
2021-12-30 14:23 ` johelegp 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-96840-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).