From: Jason Merrill <jason@redhat.com>
To: Andrew Sutton <andrew.n.sutton@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] PR c++/92439: Improve diagnostics for ill-formed requires-clauses
Date: Tue, 26 Nov 2019 21:41:00 -0000 [thread overview]
Message-ID: <1f5459eb-ee21-4fe7-7459-9adc2d0be4b0@redhat.com> (raw)
In-Reply-To: <CANq5SyuLRXBb8AjNmPkeyqYjZmrf_P4sP8jPnX4a1BJhjEROQg@mail.gmail.com>
On 11/22/19 10:28 AM, Andrew Sutton wrote:
> This does a much better job identifying when an expression in a
> requires-clause needs parentheses.
>
> Andrew Sutton
>
OK.
Jason
prev parent reply other threads:[~2019-11-26 21:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 16:08 Andrew Sutton
2019-11-26 21:41 ` Jason Merrill [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=1f5459eb-ee21-4fe7-7459-9adc2d0be4b0@redhat.com \
--to=jason@redhat.com \
--cc=andrew.n.sutton@gmail.com \
--cc=gcc-patches@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).