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. dda91b53cc53b0b42fbf47f06e9e44a8e2a2c1c5
Date: Thu, 18 Jan 2024 10:44:10 +0000 (GMT)	[thread overview]
Message-ID: <20240118104410.120EC3858C53@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  dda91b53cc53b0b42fbf47f06e9e44a8e2a2c1c5 (commit)
      from  d7b8bde61a4d4490e1baa379b843b372c5d08c15 (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 dda91b53cc53b0b42fbf47f06e9e44a8e2a2c1c5
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu Jan 18 10:43:44 2024 +0000

    Document new additions to libstdc++
    
    std::generator, std::format improvements, std::text_encoding.

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 5644de1e..951d005b 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -245,6 +245,7 @@ a work-in-progress.</p>
   <li>Improved experimental support for C++20, including:
     <ul>
     <li><code>std::chrono::parse</code>.</li>
+    <li>Unicode-aware string handling in <code>std::format</code>.</li>
     </ul>
   </li>
   <li>Improved experimental support for C++23, including:
@@ -252,6 +253,9 @@ a work-in-progress.</p>
     <li>The <code>std::ranges::to</code> function for converting
       ranges to containers.
     </li>
+    <li>The <code>std::generator</code> view for getting results from
+      coroutines.
+    </li>
     <li>The <code>&lt;stacktrace&gt;</code> header is supported by default.
     </li>
     <li><code>std::print</code> and <code>std::println</code>
@@ -272,7 +276,13 @@ a work-in-progress.</p>
     <li>Functions for saturation arithmetic on integers.</li>
     <li><code>std::to_string</code> now uses <code>std::format</code>.</li>
     <li>Enhanced formatting of pointers with <code>std::format</code>.</li>
+    <li>The <code>std::runtime_format</code> function to allow using
+      non-literal format strings with <code>std::format</code>.</li>
     <li>Testable result types for <code>&lt;charconv&gt;</code> functions.</li>
+    <li>The <code>std::text_encoding</code> class for identifying character
+      sets (requires linking with <code>-lstdc++exp</code> for some member
+      functions).
+    </li>
     </ul>
   </li>
   <li>Faster numeric conversions using <code>std::to_string</code> and

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

Summary of changes:
 htdocs/gcc-14/changes.html | 10 ++++++++++
 1 file changed, 10 insertions(+)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2024-01-18 10:44 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=20240118104410.120EC3858C53@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).