WG21 PAPERS

Mailings Beta

Volunteer-driven · Not affiliated with WG21 or ISO

Filter and export papers from the C++ Committee’s monthly mailings by time frame and audience using the options below, or refine your export further with the Select button. Links point directly to the official WG21 papers on open-std.org.

Submit Issue C++ Standards Committee Papers

1 · Year 1 · Month

Select the arrow to the right of the year to filter for specific months.

Add Year +

Select Years To Display

Current Years Selected

2026 2025

Group by date?

Select	Paper	Title	Authors	Audience	Mailing Date
	P2728R11	Unicode in the Library, Part 1: UTF Transcoding	Eddie Nolan E. Nolan	LEWG SG9 SG16	2026-02
Intent Proposal Mailing Date 2026-02 Pre-Croydon Author(s) Eddie Nolan Target Audience LEWG SG9 SG16 Revisions R15 R14 R13 R12 Tracking issue View on GitHub
	P3045R7	Quantities and units library	Mateusz Pusz M. Pusz , Dominik Berner D. Berner , Johel Ernesto Guerrero Peña J. Peña , Charles Hogg C. Hogg , Nicolas Holthaus N. Holthaus , Roth Michaels R. Michaels , Vincent Reverdy V. Reverdy	LEWG SG6 SG16 SG20	2026-02
Intent Proposal Mailing Date 2026-02 Pre-Croydon Author(s) Mateusz Pusz, Dominik Berner, Johel Ernesto Guerrero Peña, Charles Hogg, Nicolas Holthaus, Roth Michaels, Vincent Reverdy Target Audience LEWG SG6 SG16 SG20 Revisions R9 R8 R6 Tracking issue View on GitHub Abstract Several groups in the ISO C++ Committee reviewed the “P1935: A C++ Approach to Physical Units” [[P1935R2]](https://wg21.link/p1935r2) proposal in Belfast 2019 and Prague 2020. All those groups expressed interest in the potential standardization of such a library and encouraged further work. The authors also got valuable initial feedback that highly influenced the design of the V2 version of the [[
	P3688R6	ASCII character utilities	Jan Schultke J. Schultke , Corentin Jabot C. Jabot	SG16	2026-02
Intent Proposal Mailing Date 2026-02 Pre-Croydon Author(s) Jan Schultke, Corentin Jabot Target Audience SG16 Revisions R7 R1 Tracking issue View on GitHub Abstract Testing whether a character falls into a specific subset of ASCII characters or performing some simple transformations are common tasks in text processing. For example, applications may need to check if identifiers are comprised of alphanumeric ASCII characters or underscores; Unicode properties are not relevant to this task, and usually, neither are locales.
	P3876R1	Extending <charconv> support to more character types	Jan Schultke J. Schultke , Peter Bindels P. Bindels	SG16	2026-02
Intent Proposal Mailing Date 2026-02 Pre-Croydon Author(s) Jan Schultke, Peter Bindels Target Audience SG16 Revisions R3 R2 Tracking issue View on GitHub Abstract Support for `char8_t` and other Unicode character types in `std::to_chars` and `std::from_chars` is clearly useful. File formats such as JSON require the use of Unicode character encodings, so an application that deals with JSON may want to use `char8_t` in its APIs and internally. However, when attempting to use `char8_t` for this purpose, one quickly runs into problems:
	P3904R1	When paths go WTF: making formatting lossless	Victor Zverovich V. Zverovich	SG16	2026-02
Intent Proposal Mailing Date 2026-02 Pre-Croydon Author(s) Victor Zverovich Target Audience SG16 Revisions R3 R2 Tracking issue View on GitHub Abstract [P2845], adopted in C++26, added formatting support for `std::filesystem::path`, addressing encoding issues and making formatting lossless except for one case, unpaired surrogates on Windows. This paper proposes addressing this case and making formatting 100% lossless by default via the WTF-8 encoding ([WTF-8]). This will improve consistency in path handling between Windows and POSIX platforms and
	P4030R0	Endian Views	Eddie Nolan E. Nolan	LEWG SG9 SG16	2026-02
Intent Proposal Mailing Date 2026-02 Pre-Croydon Author(s) Eddie Nolan Target Audience LEWG SG9 SG16 Revisions R1 Tracking issue View on GitHub Abstract The main reason for adding these views is to assist users of the UTF transcoding range adaptors (see [[P2728R7]](https://wg21.link/p2728r7)). That paper introduces the adaptors `to_utf8`, `to_utf16`, and `to_utf32`, which take as input ranges of `char8_t`, `char16_t`, and `char32_t`. The input and output of these views use native endianness. But users often need to convert to and from UTF encoding

Showing 6 of 6 papers · source: open-std.org

Mailings Beta

Sign in