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.

Audience
General
Wording
Evolution
Study Groups
Mailings
1 · Year 1 · Month

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

2026 May · 1 of 7

Pick months in 2026

2025 143 papers

Pick months in 2025

Add Year +

Select Years To Display

Current Years Selected

2026 2025
Filters SG16 Clear all
3 out of 3 papers selected for export
SelectPaper Title Authors Audience Doc Date Mailing Date
P2728R12 Unicode in the Library, Part 1: UTF Transcoding Eddie Nolan E. Nolan 2026-05
Mailing Date 2026-05 Pre-Brno
Author(s) Eddie Nolan
Target Audience LEWGSG9SG16
Revisions R15R14R13R11
Tracking issue View on GitHub
P3045R8 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 2026-05
Mailing Date 2026-05 Pre-Brno
Target Audience LEWGSG6SG16SG20
Revisions R9R7R6
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 [[
P3876R2 Extending <charconv> support to more character types Jan Schultke J. Schultke , Peter Bindels P. Bindels 2026-05
Mailing Date 2026-05 Pre-Brno
Target Audience SG16
Revisions R3R1
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:
Showing 3 of 3 papers · source: open-std.org