From: Jonathan Wakely <jwakely@redhat.com>
To: Jason Merrill <jason@redhat.com>
Cc: Marek Polacek <polacek@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] c++: ICE with __has_unique_object_representations [PR115476]
Date: Tue, 25 Jun 2024 18:22:56 +0100 [thread overview]
Message-ID: <CACb0b4nHME=zCk63PTj3BRQfRn=ARMCWNcHnW+v7Htd=PHGTkA@mail.gmail.com> (raw)
In-Reply-To: <300bec1d-9b80-4605-adfa-1e3e59d217a8@redhat.com>
On Tue, 25 Jun 2024 at 16:17, Jason Merrill <jason@redhat.com> wrote:
>
> On 6/25/24 07:15, Jonathan Wakely wrote:
> > On Tue, 25 Jun 2024 at 03:12, Jason Merrill <jason@redhat.com> wrote:
> >>
> >> On 6/18/24 10:31, Marek Polacek wrote:
> >>> Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk/14/13?
> >>
> >> Makes sense to me, though probably the [meta.unary.prop] table should be
> >> adjusted in the same way. Jonathan, what do you think?
> >
> > Just to make sure I understand correctly, the suggestion is to change
> > the precondition for the trait to something like:
> >
> > "remove_all_extents_t<T> shall be a complete type or cv void."
> >
> > i.e. if T is incomplete then T[] cannot be used with the trait, right?
>
> Yes.
Thanks. This is now https://cplusplus.github.io/LWG/issue4113
next prev parent reply other threads:[~2024-06-25 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 14:31 Marek Polacek
2024-06-25 2:12 ` Jason Merrill
2024-06-25 11:15 ` Jonathan Wakely
2024-06-25 15:17 ` Jason Merrill
2024-06-25 17:22 ` Jonathan Wakely [this message]
2024-06-25 19:07 ` Marek Polacek
2024-06-25 21:23 ` 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='CACb0b4nHME=zCk63PTj3BRQfRn=ARMCWNcHnW+v7Htd=PHGTkA@mail.gmail.com' \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=polacek@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).