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 Oct · 1 of 8

Pick months in 2026

2025 143 papers

Pick months in 2025

Add Year +

Select Years To Display

Current Years Selected

2026 2025
Filters SG23 Clear all
9 out of 9 papers selected for export
SelectPaper Title Authors Audience Doc Date Mailing Date
P3704R1 What are profiles? Bjarne Stroustrup B. Stroustrup 2026-10-23 2026-10
Doc Date 2026-10-23
Mailing Date 2026-10 Pre-Búzios
Author(s) Bjarne Stroustrup
Target Audience EWGLEWGSG20SG23
Tracking issue View on GitHub
Abstract The aim of this note is to give a brief explanation of what Profiles are and what problems they aim to address. It also tries to dispel some myths about the scope of Profiles and give an idea of the current state of implementation.
P4222R3 An initialization profile Bjarne Stroustrup B. Stroustrup 2026-10-23 2026-10
Doc Date 2026-10-23
Mailing Date 2026-10 Pre-Búzios
Author(s) Bjarne Stroustrup
Target Audience EWGSG20SG23
Revisions R2R1R0
Tracking issue View on GitHub
Abstract This note emphasizes the rationale of the initialization profile, considers a few alternatives, and suggests simplifications. Implementations exist and are tested nightly [Impl1, Impl2].
P4392R0 C++ Tourniquet - Stricter Contracts Jarrad J. Waterloo J. Waterloo 2026-10-14 2026-10
Doc Date 2026-10-14
Mailing Date 2026-10 Pre-Búzios
Author(s) Jarrad J. Waterloo
Target Audience CWGSG23
Abstract The, mostly likely, biggest impediment to any safety proposal that impacts the language is its being backwards compatible with existing code. However, for new code blocks that should not be an impediment. Consequently, new language features can and should be made as safe as possible. It would be beneficial to the C++ community if the standard put a moratorium on adding new language features where
P4401R0 UB and profile-defined behavior Herb Sutter H. Sutter 2026-10-19 2026-10
Doc Date 2026-10-19
Mailing Date 2026-10 Pre-Búzios
Author(s) Herb Sutter
Target Audience SG23
Abstract Stroustrup gives the canonical example of how profiles might define signed overflow in [[P3984R0](https://wg21.link/p3984r0)] page 3:
P4415R0 Profiles: implementation status and experience Michael Wong M. Wong , Krystian Stasiowski ; Ville Voutilainen K. Voutilainen 2026-10-23 2026-10
Doc Date 2026-10-23
Mailing Date 2026-10 Pre-Búzios
Target Audience EWGLEWGSG23
Abstract Profiles now have two independent implementations. Krystian Stasiowski's Clang implements the P3589R2 framework, except <ins>[[profiles::exempt]]</ins>, and most of the P4222R2 initialization profile <ins>std::init</ins>. Ville Voutilainen's GCC implements the framework, <ins>std::init, and the first working invalidation profile, std::invalidation</ins>, on the design of P3446R0 with the default-d
P4416R0 Proposed wording for the initialization profile Michael Wong M. Wong , Bjarne Stroustrup B. Stroustrup 2026-10-23 2026-10
Doc Date 2026-10-23
Mailing Date 2026-10 Pre-Búzios
Target Audience CWGLWGSG23
Abstract This paper supplies proposed working-draft wording for the initialization profile described in the design paper "An initialization profile", P4222R3 [BS'26b]. The design paper states what the profile guarantees and why; this paper states the rules in the form the working draft needs, so that the two can be reviewed together and the wording can be handed to CWG and LWG once the design is approved.
P4417R0 Proposed wording for the invalidation profile Michael Wong M. Wong , Bjarne Stroustrup B. Stroustrup 2026-10-23 2026-10
Doc Date 2026-10-23
Mailing Date 2026-10 Pre-Búzios
Target Audience CWGLWGSG23
Abstract This paper supplies proposed working-draft wording for the invalidation profile described in the design paper "An invalidation profile", P4418R0 [BS'26c]. The design paper states what the profile guarantees and why; this paper states the rules in the form the working draft needs, so that the two can be reviewed together and the wording can be handed to CWG and LWG once the design is approved. The
P4418R0 An invalidation Profile Bjarne Stroustrup B. Stroustrup 2026-10-23 2026-10
Doc Date 2026-10-23
Mailing Date 2026-10 Pre-Búzios
Author(s) Bjarne Stroustrup
Target Audience EWGSG20SG23
Abstract Memory safety has been a popular topic over the last few years. It is a subset of type-and-resource safety which has been my ideal for C++ since its inception and for which the general solution for C++ was outlined in [BS’15, HS’15, BS’21]. This paper describes the enforcement part of the solution that relates to prevention of dangling pointers and its rationale.
P4422R0 Function Summaries for Scaling Code Analysis of C++ Gabriel Dos Reis G. Reis 2026-10-23 2026-10
Doc Date 2026-10-23
Mailing Date 2026-10 Pre-Búzios
Author(s) Gabriel Dos Reis
Target Audience EWGSG15SG23
Abstract Profiles [P3589R3] are to be enforced by local static analysis [P3274R0]: one translation unit at a time, and within it one function at a time. At a call to a function defined elsewhere, such an analysis has only the callee's declaration. The declaration says little about what the callee writes, and nothing about what it retains, releases or invalidates. The analysis gives the same verdict for eve
Showing 9 of 9 papers · source: open-std.org