Date: Mon, 27 Apr 2026 10:31:38 +0200
Hi,
I am planning another meeting in 2-3 weeks. The following papers are
scheduled:
- P3677R0 <https://wg21.link/p3677r0> Preserving LC_CTYPE at program
start for UTF-8 locales (Corentin Jabot)
- P3935R0 <https://wg21.link/p3935r0> Rebasing <cmath> on C23 (Jan
Schultke)
*https://doodle.com/group-poll/participate/aAXLlO1e
<https://doodle.com/group-poll/participate/aAXLlO1e> Please fill out this
Doodle poll so we know what times work for you.*
I've made sure not to conflict with the CWG telecon Tu 2026-05-12. There is
an SG16 Telecon immediately following the second time slot We 2026-05-13.
I've also put some work into the SG22 GitHub repository at
https://github.com/sg22-c-cpp-standard-compatibility/sg-compatibility
yesterday. Note the following updates:
- All meeting notes have been moved into the meetings directory. You can
also find the notes for our 2026-04-24 meeting there.
- Various completed issues in the repository have been closed, and many
new issues for C2y papers that are of interest to C++ have been opened.
- There is a work-in-progress page at
https://github.com/sg22-c-cpp-standard-compatibility/sg-compatibility/blob/main/c2y-compatibility.md
tracking the compatibility status between C2y and C++. This provides a
summary of all adopted C2y changes and what we're doing on the C++ side.
Note that this isn't meant to imply that every change to C automatically
needs to be adopted in C++, but deciding to adopt changes from C usually
needs to be a conscious decision (in favor or against), especially for
library features.
Yours
Jan Schultke
I am planning another meeting in 2-3 weeks. The following papers are
scheduled:
- P3677R0 <https://wg21.link/p3677r0> Preserving LC_CTYPE at program
start for UTF-8 locales (Corentin Jabot)
- P3935R0 <https://wg21.link/p3935r0> Rebasing <cmath> on C23 (Jan
Schultke)
*https://doodle.com/group-poll/participate/aAXLlO1e
<https://doodle.com/group-poll/participate/aAXLlO1e> Please fill out this
Doodle poll so we know what times work for you.*
I've made sure not to conflict with the CWG telecon Tu 2026-05-12. There is
an SG16 Telecon immediately following the second time slot We 2026-05-13.
I've also put some work into the SG22 GitHub repository at
https://github.com/sg22-c-cpp-standard-compatibility/sg-compatibility
yesterday. Note the following updates:
- All meeting notes have been moved into the meetings directory. You can
also find the notes for our 2026-04-24 meeting there.
- Various completed issues in the repository have been closed, and many
new issues for C2y papers that are of interest to C++ have been opened.
- There is a work-in-progress page at
https://github.com/sg22-c-cpp-standard-compatibility/sg-compatibility/blob/main/c2y-compatibility.md
tracking the compatibility status between C2y and C++. This provides a
summary of all adopted C2y changes and what we're doing on the C++ side.
Note that this isn't meant to imply that every change to C automatically
needs to be adopted in C++, but deciding to adopt changes from C usually
needs to be a conscious decision (in favor or against), especially for
library features.
Yours
Jan Schultke
Received on 2026-04-27 08:31:52
