public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
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] wwwdocs: Document more libstdc++ additions for GCC 13
Date: Wed, 26 Apr 2023 13:52:48 +0100	[thread overview]
Message-ID: <CACb0b4kPhNi10gS3O+mA1zz6HTFzySaQM56VXkVQuyNbmw4zfg@mail.gmail.com> (raw)
In-Reply-To: <20230426125140.1064474-1-ppalka@redhat.com>

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

On Wed, 26 Apr 2023 at 13:52, Patrick Palka via Libstdc++ <
libstdc++@gcc.gnu.org> wrote:

> Does this look OK for wwwdocs?
>
> ---
>  htdocs/gcc-13/changes.html | 12 +++++++++++-
>  1 file changed, 11 insertions(+), 1 deletion(-)
>
> diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
> index 7b64b2e5..191d0a4d 100644
> --- a/htdocs/gcc-13/changes.html
> +++ b/htdocs/gcc-13/changes.html
> @@ -370,7 +370,17 @@ You may also want to check out our
>        <code>views::pairwise</code>, <code>views::slide</code>,
>        <code>views::chunk</code>, <code>views::chunk_by</code>,
>        <code>views::repeat</code>, <code>views::chunk_by</code>,
> -      <code>views::cartesian_product</code>,
> <code>views::as_rvalue</code>.
> +      <code>views::cartesian_product</code>,
> <code>views::as_rvalue</code>,
> +      <code>views::enumerate</code>, <code>views::as_const</code>.
> +    </li>
> +    <li>Additions to the <code>&lt;algorithm&gt;</code> header:
> +      <code>ranges::contains</code>,
> <code>ranges::contains_subrange</code>,
> +      <code>ranges::iota</code>, <code>ranges::find_last</code>,
> +      <code>ranges::find_last_if</code>,
> <code>ranges::find_last_if_not</code>,
> +      <code>ranges::fold_left</code>,
> <code>ranges::fold_left_first</code>,
> +      <code>ranges::fold_right</code>,
> <code>ranges::fold_right_last</code>,
> +      <code>ranges::fold_left_with_iter</code>
>

OK with a comma at the end of the line above, thanks.


> +      <code>ranges::fold_left_first_with_iter</code>.
>      </li>
>      <li>Monadic operations for <code>std::expected</code>.</li>
>      <li>Constexpr <code>std::bitset</code>, <code>std::to_chars</code>
> --
> 2.40.1.423.g2807bd2c10
>
>

      reply	other threads:[~2023-04-26 12:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-26 12:51 Patrick Palka
2023-04-26 12:52 ` 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=CACb0b4kPhNi10gS3O+mA1zz6HTFzySaQM56VXkVQuyNbmw4zfg@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).