public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marek Polacek <polacek@redhat.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: [wwwdocs] cxx-status: Add C++23 papers from the Nov 2022 Kona WG21 plenary
Date: Mon, 14 Nov 2022 13:54:26 -0500	[thread overview]
Message-ID: <Y3KO4nPza2D9nJMQ@redhat.com> (raw)

Pushed.

commit b97d1aba41d95ae9220fe08a991738a58a716212
Author: Marek Polacek <polacek@redhat.com>
Date:   Mon Nov 14 13:49:21 2022 -0500

    cxx-status: Add C++23 papers from the Nov 2022 Kona WG21 plenary

diff --git a/htdocs/projects/cxx-status.html b/htdocs/projects/cxx-status.html
index 8650f3cd..3454cfc9 100644
--- a/htdocs/projects/cxx-status.html
+++ b/htdocs/projects/cxx-status.html
@@ -356,6 +356,42 @@
       <td class="unsupported"> <a href="https://gcc.gnu.org/PR106658">No</a></td>
       <td> </td>
     </tr>
+    <!--  Kona 2022, https://github.com/cplusplus/papers/issues/1247 -->
+    <tr>
+      <td> <code>static operator[]</code> </td>
+      <td> <a href="https://wg21.link/p2589">P2589R1</a></td>
+      <td class="unsupported"> <a href="https://gcc.gnu.org/PR107684">No</a></td>
+      <td> __cpp_multidimensional_subscript >= 202211L </td>
+    </tr>
+    <!-- Kona 2022, https://github.com/cplusplus/papers/issues/1318 -->
+    <tr>
+      <td> DR: Permitting <code>static constexpr</code> variables in
+	  <code>constexpr</code> functions </td>
+      <td> <a href="https://wg21.link/p2647">P2647R1</a></td>
+      <td class="unsupported"> <a href="https://gcc.gnu.org/PR107685">No</a></td>
+      <td> __cpp_constexpr >= 202211L </td>
+    </tr>
+    <!-- Kona 2022, https://github.com/cplusplus/papers/issues/1223 -->
+    <tr>
+      <td> DR: <code>consteval</code> needs to propagate up </td>
+      <td> <a href="https://wg21.link/p2564">P2564R3</a></td>
+      <td class="unsupported"> <a href="https://gcc.gnu.org/PR107687">No</a></td>
+      <td> __cpp_consteval >= 202211L </td>
+    </tr>
+    <!-- Kona 2022, https://github.com/cplusplus/papers/issues/1236 -->
+    <tr>
+      <td> DR: Meaningful exports </td>
+      <td> <a href="https://wg21.link/p2615">P2615R1</a></td>
+      <td class="unsupported"> <a href="https://gcc.gnu.org/PR107688">No</a></td>
+      <td> </td>
+    </tr>
+    <!-- Kona 2022, https://github.com/cplusplus/papers/issues/1316 -->
+    <tr>
+      <td> Wording for P2644R1 Fix for Range-based for Loop </td>
+      <td> <a href="https://wg21.link/p2718">P2718R0</a></td>
+      <td class="unsupported"> <a href="https://gcc.gnu.org/PR107637">No</a></td>
+      <td> </td>
+    </tr>
     <!--
     <tr>
       <td> </td>


                 reply	other threads:[~2022-11-14 18:54 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=Y3KO4nPza2D9nJMQ@redhat.com \
    --to=polacek@redhat.com \
    --cc=gcc-patches@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).