public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. bbbf05e7f3d3e7a74d23e8cc252ebae895158abe
Date: Mon,  7 Jun 2021 09:27:09 +0000 (GMT)	[thread overview]
Message-ID: <20210607092709.978833857020@sourceware.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".

The branch, master has been updated
       via  bbbf05e7f3d3e7a74d23e8cc252ebae895158abe (commit)
      from  3733fbc6c15211ee367d0329cb2f57f29bfb1e83 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit bbbf05e7f3d3e7a74d23e8cc252ebae895158abe
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Mon Jun 7 10:27:00 2021 +0100

    Document libstdc++ support for generic unordered lookup

diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index ef533e31..97606174 100644
--- a/htdocs/gcc-11/changes.html
+++ b/htdocs/gcc-11/changes.html
@@ -526,6 +526,7 @@ You may also want to check out our
         and <code>&lt;semaphore&gt;</code></li>
       <li><code>&lt;syncstream&gt;</code></li>
       <li>Efficient access to <code>basic_stringbuf</code>'s buffer.</li>
+      <li>Heterogeneous lookup in unordered containers.</li>
     </ul>
   </li>
   <li>Experimental C++23 support, including:

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gcc-11/changes.html | 1 +
 1 file changed, 1 insertion(+)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2021-06-07  9:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210607092709.978833857020@sourceware.org \
    --to=redi@sourceware.org \
    --cc=gcc-cvs-wwwdocs@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).