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 Jan · 1 of 6

Pick months in 2026

Add Year +

Select Years To Display

Current Years Selected

2026
Filters EWG Clear all
8 out of 8 papers selected for export
SelectPaper Title Authors Audience Doc Date
P3039R1 Automatically Generate `operator->` A. Kostur, D. Stone
Intent Proposal
Mailing Date 2026-01 Unassigned
Target Audience EWGLEWG
Tracking issue View on GitHub
P3865R1 Class template argument deduction (CTAD) for type template template parameters C. Meerwald
Intent Proposal
Mailing Date 2026-01 Unassigned
Author(s) Christof Meerwald
Target Audience EWG
Revisions R3R2
Tracking issue View on GitHub
Abstract [CWG 3003](https://cplusplus.github.io/CWG/issues/3003.html) "Naming a deducible template for class template argument deduction" has been raised to clarify that with the current core language wording, class template argument deduction does not work for type template template parameters.
P3911R2 RO 2-056 6.11.2 [basic.contract.eval] Make Contracts Reliably Non-Ignorable D. Neațu, A. Alexandrescu, L. Teodorescu, R. Nichita, H. Sutter
Intent Proposal
Mailing Date 2026-01 Unassigned
Target Audience EWGSG21
Revisions R1
Tracking issue View on GitHub
Abstract Building on motivation from EWG Kona 2025, this paper proposes a minimal pure extension to the C++26 Contracts facility. This extension addresses the Romanian National Body's (NB) concern by enabling the writing of an individual contract assertion that guarantees the program execution will not continue past the contract assertion if it is violated, regardless of the semantics of other contract ass
P3950R0 return_value & return_void Are Not Mutually Exclusive R. Leahy
Intent Proposal
Mailing Date 2026-01 Unassigned
Author(s) Robert Leahy
Target Audience EWGSG1SG17
Revisions R1
Tracking issue View on GitHub
Abstract The standard specifies the effect of `co_return` statements in terms of equivalent statements within the context of a *replacement body* (§9.6.4 [dcl.fct.def.coroutine]). Like a regular `return` statement `co_return` statements have two distinct forms: Those that return `void` and those that return some value. These are specified as follows (§8.8.5 [stmt.return.coroutine]):
P3951R0 String Interpolation Objects B. Revzin
Intent Proposal
Mailing Date 2026-01 Unassigned
Author(s) Barry Revzin
Target Audience EWG
Revisions R1
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,
P3952R0 is_pointer_in_range H. Sutter, G. Fernandes
Intent Proposal
Mailing Date 2026-01 Unassigned
Target Audience EWGLEWG
Tracking issue View on GitHub
Abstract WG21 is often asked for a way to reliably answer the question, “does this raw pointer point inside this buffer?” See [Core 2025] for some use cases. Such an `is_pointer_in_range` function is appropriate to standardize because:
P3960R0 Define copy-constructibility-from-bytes M. Hoemmen, R. Arutyunyan
Intent Proposal
Mailing Date 2026-01 Unassigned
Target Audience EWGLEWGSG1SG17
Tracking issue View on GitHub
Abstract Given an object `src` of trivially-copyable type `T`, we can copy the object’s value representation to an array of bytes, and implicitly create a new `T` object (e.g., with `start_lifetime_as`) in the array of bytes. The result will hold the same value as `src`.
P3963R0 Assignable lambdas with capture R. Arutyunyan
Intent Proposal
Mailing Date 2026-01 Unassigned
Author(s) Ruslan Arutyunyan
Target Audience EWGSG17
Tracking issue View on GitHub
Abstract This paper proposes making lambdas with captures copy assignable and move assignable when all captured entities are themselves assignable.
Showing 8 of 8 papers · source: open-std.org