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
	P3951R1	String Interpolation Objects	Barry Revzin B. Revzin	EWG	2026-04
Intent Proposal Mailing Date 2026-04 Post-Croydon Author(s) Barry Revzin Target Audience EWG Revisions R2 R0 Tracking issue View on GitHub Abstract The `std::format` approach to formatting offers many significant benefits over the prior `<iostream>`s approach that need not be revisited here. However, `<iostream>` does still have one significant advantage: ordering. It is easy to see at a glance with a long `std::cout` statement which pieces are to be formatted in which order. With `std::format`, as the amount of replacement fields increases,
	P4101R0	Consteval-only Values for C++26	Barry Revzin B. Revzin , Peter Dimov P. Dimov , Daveed Vandevoorde D. Vandevoorde , Dan Katz D. Katz	EWG CWG	2026-04
Intent Proposal Mailing Date 2026-04 Post-Croydon Author(s) Barry Revzin, Peter Dimov, Daveed Vandevoorde, Dan Katz Target Audience EWG CWG Revisions R1 Tracking issue View on GitHub Abstract The Reflection design from [[P2996R13]](https://wg21.link/p2996r13) was based on a model of having consteval-only types to prevent reflections from leaking to runtime. But we’ve run into issues and limitations with that approach, so we propose that, for C++26, we change instead to a consteval-only value model. This solves the same problems, but has additional benefits.

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

Mailings Beta

Sign in