From: Jonathan Wakely <jwakely@redhat.com>
To: Patrick Palka <ppalka@redhat.com>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [PATCH] libstdc++: Fix ranges::join_view::_Iterator::operator-> [LWG 3500]
Date: Wed, 18 Nov 2020 14:17:33 +0000 [thread overview]
Message-ID: <20201118141733.GE503596@redhat.com> (raw)
In-Reply-To: <20201118141024.890389-1-ppalka@redhat.com>
On 18/11/20 09:10 -0500, Patrick Palka via Libstdc++ wrote:
>This applies the proposed resolution of LWG 3500, which corrects the
>return type and constraints of this member function to use the right
>iterator type. Additionally, a nearby local variable is uglified.
>
>Tested on x86_64-pc-linux-gnu, does this look OK for trunk and the 10
>branch?
OK, thanks.
prev parent reply other threads:[~2020-11-18 14:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 14:10 Patrick Palka
2020-11-18 14:17 ` 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=20201118141733.GE503596@redhat.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).