public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nickgray0 at brown dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99518] trailing requires clause adds nonexistent reference declarator to function parameter
Date: Wed, 10 Mar 2021 15:46:55 +0000	[thread overview]
Message-ID: <bug-99518-4-VgwD8yGOyR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99518-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from nickgray0 at brown dot edu ---
I just looked up the standard and it seems GCC is correct to reject the code
and Clang's implementation (which happily compiles the code) is incorrect. the
compound requirement requires the parenthesized expression (which in this case,
turns 'x' to int&) to satisfy the return type constraint.

Sorry for the false alarm.

  reply	other threads:[~2021-03-10 15:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10 14:32 [Bug c++/99518] New: " nickgray0 at brown dot edu
2021-03-10 15:46 ` nickgray0 at brown dot edu [this message]
2021-03-10 15:48 ` [Bug c++/99518] " nickgray0 at brown dot edu

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-99518-4-VgwD8yGOyR@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).