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	Doc Date	Mailing Date
	P3566R2	You shall not pass `char*` - Safety concerns working with unbounded null-terminated strings	Marco Foco M. Foco , Joshua Kriegshauser J. Kriegshauser , Alexey Shevlyakov A. Shevlyakov , Giuseppe D'Angelo G. D'Angelo	LEWG SG18 SG23	2025-06-16	2025-07
Doc Date 2025-06-16 Mailing Date 2025-07 Post-Sofia Author(s) Marco Foco, Joshua Kriegshauser, Alexey Shevlyakov, Giuseppe D'Angelo Target Audience LEWG SG18 SG23 Tracking issue View on GitHub Abstract `string`s and `string_view`s are often used as a safer alternative to null-terminated strings. Unfortunately they suffer from an implicit assumption at creation/assignment time, and in some of their functions: the presence of a null-terminator in the input sequence. The absence of the null-terminator can currently lead to undefined behavior inside these functions. There are many cases when the len
	P3711R1	Safer StringViewLike Functions for Replacing char* strings	Marco Foco M. Foco , Alexey Shevlyakov A. Shevlyakov , Joshua Kriegshauser J. Kriegshauser	LEWG SG23	2025-06-20	2025-07
Doc Date 2025-06-20 Mailing Date 2025-07 Post-Sofia Author(s) Marco Foco, Alexey Shevlyakov, Joshua Kriegshauser Target Audience LEWG SG23 Tracking issue View on GitHub Abstract This document introduces a set of string utility functions that we used in NVIDIA Omniverse Foundation Library, and were key components to remove `char` (or more generally `CharT`) strings usage from our codebase replacing them with the implementation proposed in P3566. All the usages that will still need to use the old-fashioned `char*`s will be marked accordingly to P3566, using the proposed `

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

Mailings Beta

Sign in