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 1/2] libstdc++: Move some ranges algos to a new header <bits/ranges_algobase.h>
Date: Thu, 13 Feb 2020 12:20:00 -0000 [thread overview]
Message-ID: <20200213122030.GE9441@redhat.com> (raw)
In-Reply-To: <20200212204107.4124217-1-ppalka@redhat.com>
On 12/02/20 15:41 -0500, Patrick Palka wrote:
>This roughly mirrors the existing split between <bits/stl_algo.h> and
><bits/stl_algobase.h>. The ranges [specialized.algorithms] will use this new
>header to avoid including all of of <bits/ranges_algo.h>.
>
>libstdc++-v3/ChangeLog:
>
> * include/Makefile.am: Add bits/ranges_algobase.h
> * include/Makefile.in: Regenerate.
> * bits/ranges_algo.h: Include <bits/ranges_algobase.h> and refactor
> existing #includes.
> (__detail::__is_normal_iterator, __detail::is_reverse_iterator,
> __detail::__is_move_iterator, copy_result, move_result,
> __equal, equal, copy_result, move_result, move_backward_result,
> copy_backward_result, __copy_or_move_backward, __copy_or_move, copy,
> move, copy_backward, move_backward, copy_n_result, copy_n, fill_n,
> fill): Split out into ...
> * bits/range_algobase.h: ... this new header.
OK for master.
prev parent reply other threads:[~2020-02-13 12:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 20:42 Patrick Palka
2020-02-12 20:42 ` [PATCH 2/2] libstdc++: Implement ranges [specialized.algorithms] Patrick Palka
2020-02-13 16:12 ` Jonathan Wakely
2020-02-13 20:46 ` Patrick Palka
2020-02-13 12:20 ` 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=20200213122030.GE9441@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).