From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Patrick Palka <ppalka@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
"libstdc++" <libstdc++@gcc.gnu.org>
Subject: Re: [PATCH 2/5] libstdc++: Move ranges algos used by <ranges> into ranges_util.h
Date: Thu, 17 Jun 2021 19:14:47 +0100 [thread overview]
Message-ID: <CAH6eHdRJGZCr2TKScT-bb3DE32o6jXGVoVdjZT-rhQy3_xtD+g@mail.gmail.com> (raw)
In-Reply-To: <20210617152206.1408001-2-ppalka@redhat.com>
On Thu, 17 Jun 2021, 16:47 Patrick Palka via Libstdc++, <
libstdc++@gcc.gnu.org> wrote:
> The <ranges> header defines simplified copies of some ranges algorithms
> in order to avoid including the entirety of ranges_algo.h. A subsequent
> patch is going to want to use ranges::search in <ranges> as well, but
> that algorithm is more complicated compared to the other copied ones.
>
> So rather than additionally copying ranges::search into <ranges>, this
> patch splits out all the ranges algos used by <ranges> (including
> ranges::search) from ranges_algo.h to ranges_util.h, and deletes the
> simplified copies in <ranges>. This seems like the best place for
> these algorithms, as ranges_util.h is included only from <ranges> and
> ranges_algo.h.
>
OK, thanks.
next prev parent reply other threads:[~2021-06-17 18:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 15:22 [PATCH 1/5] libstdc++: Implement P2325 changes to default-constructibilty of views Patrick Palka
2021-06-17 15:22 ` [PATCH 2/5] libstdc++: Move ranges algos used by <ranges> into ranges_util.h Patrick Palka
2021-06-17 18:14 ` Jonathan Wakely [this message]
2021-06-17 15:22 ` [PATCH 3/5] libstdc++: Rename views::split to views::lazy_split as per P2210 Patrick Palka
2021-06-18 21:56 ` Jonathan Wakely
2021-06-17 15:22 ` [PATCH 4/5] libstdc++: Implement resolution of LWG 3478 " Patrick Palka
2021-06-18 21:57 ` Jonathan Wakely
2021-06-17 15:22 ` [PATCH 5/5] libstdc++: Implement new views::split " Patrick Palka
2021-06-18 21:58 ` Jonathan Wakely
2021-06-17 18:19 ` [PATCH 1/5] libstdc++: Implement P2325 changes to default-constructibilty of views Jonathan Wakely
2021-06-17 18:28 ` Jonathan Wakely
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=CAH6eHdRJGZCr2TKScT-bb3DE32o6jXGVoVdjZT-rhQy3_xtD+g@mail.gmail.com \
--to=jwakely.gcc@gmail.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).