N.B. you can use the first post-C23 working draft https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3220.pdf to see the content of C23. As explained in the editor's report, N3221, it has the same technical content as the C23 DIS except for one word added to a footnote.

I linked to a password-protected C draft in the google doc, which wasn't very helpful.


On Tue, 2 Jul 2024 at 23:09, Inbal Levi <sinbal2l@gmail.com> wrote:

Best Regards,
Inbal Levi

ISO C++ LEWG Chair & Israeli NB Chair
C++Now Program Chair & CoreC++ Conference Organizer


On Wed, 3 Jul 2024 at 01:02, Inbal Levi <sinbal2l@gmail.com> wrote:
Hello all!
As we've discussed lately, there is a need to rebase C++26 on C23.
Jonathan kindly started the work on this by posting this thread:

Which later turned into a doc, on which he added the proper changes under section "IV. Draft Proposal":

There are 8 design decisions there, so review this efficiently:
  1. I would ask that you reply to this thread in advance with reasoning for design decisions:
    1. Along the document, there are sentences marked in light blue with a number (x), these are design decisions to be made (either by LEWG alone or with input from other groups, e.g. SG6 (numerics)).
    2. Please kindly reply (but not to EWG) with your recommendations and reasoning, by stating the number and the recommendation and reasoning. For example:

      (2)       (macros are marked as obsolescent)
      I would recommend marking them as obsolescent as well to avoid divergence from C.

  3. We will review these decisions + recommendations in an LEWG telecon, on July 30 (15:00 UTC).

Thank you in advance for your input, and special thanks to Jonathan for taking this important job upon himself!


Best Regards,
Inbal Levi

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Lead Software Engineer @ Millennium
Isocpp, Boost &"Hamakor" Non-Profits Board Member
ISO C++ LEWG Chair & Israeli NB Chair
C++Now Program Chair & CoreC++ Conference Organizer
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~