public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Jason Merrill <jason@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 0ba89730c06d6078b1cc3d675d50e491ab73566f
Date: Wed,  9 Feb 2022 19:49:08 +0000 (GMT)	[thread overview]
Message-ID: <20220209194908.7C7013858D1E@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  0ba89730c06d6078b1cc3d675d50e491ab73566f (commit)
      from  c10a88c63d8495ca282d80d149d6f8c5d122b1e5 (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 0ba89730c06d6078b1cc3d675d50e491ab73566f
Author: Jason Merrill <jason@redhat.com>
Date:   Wed Feb 9 14:48:33 2022 -0500

    cxx-status: add P2255, trait for temp ref bind

diff --git a/htdocs/projects/cxx-status.html b/htdocs/projects/cxx-status.html
index fe5d9d8c..65305bb1 100644
--- a/htdocs/projects/cxx-status.html
+++ b/htdocs/projects/cxx-status.html
@@ -226,6 +226,12 @@
       <td class="supported"> 9 </td>
       <td> </td>
     </tr>
+    <tr>
+      <td> A type trait to detect reference binding to temporary </td>
+      <td> <a href="https://wg21.link/p2255r2">P2255R2</a></td>
+      <td class="unsupported"> <a href="https://gcc.gnu.org/PR104477">No</a> </td>
+      <td> </td>
+    </tr>
     <!--
     <tr>
       <td> </td>

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

Summary of changes:
 htdocs/projects/cxx-status.html | 6 ++++++
 1 file changed, 6 insertions(+)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2022-02-09 19:49 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=20220209194908.7C7013858D1E@sourceware.org \
    --to=jason@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).