From: Jonathan Wakely <jwakely@redhat.com>
To: Patrick Palka <ppalka@redhat.com>
Cc: gcc Patches <gcc-patches@gcc.gnu.org>,
"libstdc++" <libstdc++@gcc.gnu.org>
Subject: Re: [PATCH] libstdc++: Implement LWG 3595 changes to common_iterator
Date: Wed, 20 Oct 2021 19:58:41 +0100 [thread overview]
Message-ID: <CACb0b4k7m04gR1Zp70O-LB=TOoXWepkXZ7dsY_zxyfgMA+n3jA@mail.gmail.com> (raw)
In-Reply-To: <20211020170026.1827253-1-ppalka@redhat.com>
On Wed, 20 Oct 2021 at 18:04, Patrick Palka via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
>
> Tested on x86_64-pc-linux-gnu, does this look OK for trunk and branches?
I thought I'd already done this one, maybe I have it in a local Git stash.
OK for all branches, thanks.
>
> libstdc++-v3/ChangeLog:
>
> * include/bits/stl_iterator.h (common_iterator::__arrow_proxy):
> Make fully constexpr.
> (common_iterator::__postfix_proxy): Likewise.
> ---
> libstdc++-v3/include/bits/stl_iterator.h | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/libstdc++-v3/include/bits/stl_iterator.h b/libstdc++-v3/include/bits/stl_iterator.h
> index 8afd6756613..da3c8d5bd97 100644
> --- a/libstdc++-v3/include/bits/stl_iterator.h
> +++ b/libstdc++-v3/include/bits/stl_iterator.h
> @@ -1821,13 +1821,13 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
> {
> iter_value_t<_It> _M_keep;
>
> - __arrow_proxy(iter_reference_t<_It>&& __x)
> + constexpr __arrow_proxy(iter_reference_t<_It>&& __x)
> : _M_keep(std::move(__x)) { }
>
> friend class common_iterator;
>
> public:
> - const iter_value_t<_It>*
> + constexpr const iter_value_t<_It>*
> operator->() const noexcept
> { return std::__addressof(_M_keep); }
> };
> @@ -1836,13 +1836,13 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
> {
> iter_value_t<_It> _M_keep;
>
> - __postfix_proxy(iter_reference_t<_It>&& __x)
> + constexpr __postfix_proxy(iter_reference_t<_It>&& __x)
> : _M_keep(std::forward<iter_reference_t<_It>>(__x)) { }
>
> friend class common_iterator;
>
> public:
> - const iter_value_t<_It>&
> + constexpr const iter_value_t<_It>&
> operator*() const noexcept
> { return _M_keep; }
> };
> --
> 2.33.1.711.g9d530dc002
>
prev parent reply other threads:[~2021-10-20 18:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 17:00 Patrick Palka
2021-10-20 18:58 ` Jonathan Wakely [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='CACb0b4k7m04gR1Zp70O-LB=TOoXWepkXZ7dsY_zxyfgMA+n3jA@mail.gmail.com' \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--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).