From: Jonathan Wakely <jwakely@redhat.com>
To: Patrick Palka <ppalka@redhat.com>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org, jason@redhat.com
Subject: Re: [PATCH 2/2] c++: implement __remove_cv, __remove_reference and __remove_cvref
Date: Tue, 27 Sep 2022 21:27:12 +0100 [thread overview]
Message-ID: <CACb0b4kw2H-dvJZRwhQY6+_m=NDvucT3+afQoJZs4n1xbxP2Dg@mail.gmail.com> (raw)
In-Reply-To: <20220927195030.2024439-2-ppalka@redhat.com>
On Tue, 27 Sept 2022 at 20:50, Patrick Palka via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
> libstdc++-v3/ChangeLog:
>
> * include/bits/unique_ptr.h (unique_ptr<_Tp[], _Dp>): Remove
> __remove_cv and use __remove_cv_t instead.
This part is OK. I added that __remove_cv in 2012, and could have
replaced it with __remove_cv_t when I added that in 2019.
next prev parent reply other threads:[~2022-09-27 20:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 19:50 [PATCH 1/2] c++: introduce TRAIT_TYPE alongside TRAIT_EXPR Patrick Palka
2022-09-27 19:50 ` [PATCH 2/2] c++: implement __remove_cv, __remove_reference and __remove_cvref Patrick Palka
2022-09-27 20:27 ` Jonathan Wakely [this message]
2022-09-27 21:09 ` Jason Merrill
2022-09-27 21:07 ` [PATCH 1/2] c++: introduce TRAIT_TYPE alongside TRAIT_EXPR Jason Merrill
2022-09-28 16:36 ` Patrick Palka
2022-09-28 18:49 ` 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='CACb0b4kw2H-dvJZRwhQY6+_m=NDvucT3+afQoJZs4n1xbxP2Dg@mail.gmail.com' \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=libstdc++@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).