public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: "François Dumont" <frs.dumont@gmail.com>
Cc: "libstdc++" <libstdc++@gcc.gnu.org>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Move std::search into algobase.h
Date: Wed, 31 May 2023 18:55:41 +0100	[thread overview]
Message-ID: <CACb0b4=Z+jojRW4JQ_C2nvhe0uwKNf-Nm9q6qYFMTosDoGEQ8Q@mail.gmail.com> (raw)
In-Reply-To: <01f2b9e7-14e8-12a7-c275-7e48e3bd94df@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]

On Wed, 31 May 2023 at 18:39, François Dumont via Libstdc++ <
libstdc++@gcc.gnu.org> wrote:

> libstdc++: Reduce <functional> inclusion to <stl_algobase.h>
>
>
> Move the std::search definition from stl_algo.h to stl_algobase.h and use
> the later in <functional>.
>
> For consistency also move std::__parallel::search and associated helpers
> from
> <parallel/stl_algo.h> to <parallel/stl_algobase.h> so that
> std::__parallel::search
> is accessible along with std::search.
>
> libstdc++-v3/ChangeLog:
>
>              * include/bits/stl_algo.h
>              (std::__search, std::search(_FwdIt1, _FwdIt1, _FwdIt2,
> _FwdIt2, _BinPred)): Move...
>              * include/bits/stl_algobase.h: ...here.
>              * include/std/functional: Replace <stl_algo.h> include by
> <stl_algobase.h>.
>              * include/parallel/algo.h (std::__parallel::search<_FIt1,
> _FIt2, _BinaryPred>)
>              (std::__parallel::__search_switch<_FIt1, _FIt2,
> _BinaryPred, _ItTag1, _ItTag2>):
>              Move...
>              * include/parallel/algobase.h: ...here.
>              * include/std/functional: Remove <bits/stl_algo.h> and
> <parallel/algorithm>
>              includes. Include <bits/stl_algobase.h>.
>
> Tested under Linux x86_64.
>
> Ok to commit ?
>

OK

  reply	other threads:[~2023-05-31 17:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-31 17:39 François Dumont
2023-05-31 17:55 ` Jonathan Wakely [this message]
2023-06-01 11:52   ` Rainer Orth
2023-06-01 12:05     ` Jonathan Wakely
2023-06-01 13:50       ` François Dumont
2023-06-01 20:36       ` François Dumont
2023-06-01 21:57         ` Jonathan Wakely
2023-06-02  7:33           ` François Dumont
2023-06-02  7:43             ` Jonathan Wakely
2023-06-02  9:47               ` François Dumont
2023-06-02 11:30                 ` Jonathan Wakely
2023-06-02 12:34                   ` 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='CACb0b4=Z+jojRW4JQ_C2nvhe0uwKNf-Nm9q6qYFMTosDoGEQ8Q@mail.gmail.com' \
    --to=jwakely@redhat.com \
    --cc=frs.dumont@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    /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).