public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jason Merrill <jason@redhat.com>
To: Patrick Palka <ppalka@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] c++: improve class NTTP object pretty printing [PR111471]
Date: Thu, 21 Sep 2023 16:53:36 +0100	[thread overview]
Message-ID: <2c4d035c-72d3-827c-b5df-2be34882027b@redhat.com> (raw)
In-Reply-To: <84218f4d-299b-0e93-2d11-e860ec1d925a@idea>

On 9/20/23 10:13, Patrick Palka wrote:
> On Tue, 19 Sep 2023, Patrick Palka wrote:
> 
>> On Tue, 19 Sep 2023, Jason Merrill wrote:
>>
>>> On 9/19/23 12:40, Patrick Palka wrote:
>>>> Tested on x86_64-pc-linux-gnu, does this look OK for trunk/13?
>>>
>>> OK for trunk.  What's your argument for backporting?
>>
>> Thanks.  I don't feel strongly about it, but I was thinking that since
>> we typically backport C++20-only correctness fixes to the most recent
>> release branch, C++20-only diagnostic improvements might be suitable
>> too?
>>
>>>
>>>> -- >8 --
>>>>
>>>> 1. Move class NTTP object pretty printing to a more general spot in
>>>>      the pretty printer.
> 
> FWIW this first change isn't just a refactoring, it means we now pretty
> print an NTTP object that appears elsewhere besides in a template
> argument list, e.g. in a parameter mapping:
> 
> Before:
> 
> diagnostic19.C:8:15: note: the expression ‘((const A)V).value [with V = _ZTAXtl1AEE]’ evaluated to ‘false’
> 
> After:
> 
> diagnostic19.C:8:15: note: the expression ‘(V).value [with V = A{false}]’ evaluated to ‘false’

Ah, that is a pretty big improvement.  The patch is OK.

Jason


  reply	other threads:[~2023-09-21 15:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19 16:40 Patrick Palka
2023-09-19 17:01 ` Jason Merrill
2023-09-19 17:33   ` Patrick Palka
2023-09-20 14:13     ` Patrick Palka
2023-09-21 15:53       ` Jason Merrill [this message]
2023-09-22  9:18         ` Jason Merrill

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=2c4d035c-72d3-827c-b5df-2be34882027b@redhat.com \
    --to=jason@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ppalka@redhat.com \
    /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).