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

	Paper	Title	Authors	Audience
	P4133R0	Should WG21 Even See This Paper? Admission Gates for Library and Language Proposals	V. Falco	WG21
Intent Inform Mailing Date 2026-07 Post-Brno Author(s) Vinnie Falco Target Audience WG21 Tracking issue View on GitHub Abstract The committee has never established a criterion for what belongs in the standard library. This paper supplies one.
	P4302R0	Require One Published Mailing Before Any Poll	V. Falco	WG21
Intent Ask Mailing Date 2026-07 Post-Brno Author(s) Vinnie Falco Target Audience WG21 Tracking issue View on GitHub Abstract The committee takes recorded polls on paper revisions that were never published in a mailing.
	P4306R0	Configuring Runtime Checking: Profiles and Implicit Contract Assertions	V. Falco, V. Voutilainen	WG21
Intent Inform Mailing Date 2026-07 Post-Brno Author(s) Vinnie Falco, Ville Voutilainen Target Audience WG21 Tracking issue View on GitHub Abstract Measured against the committee's own criteria, none of them awards ownership of runtime-checking configuration to either proposal.
	P4310R0	Hasta la Vista, Undefined Behavior: Why Implicit Contract Violations Should Terminate	V. Falco, V. Voutilainen	WG21
Intent Inform Mailing Date 2026-07 Post-Brno Author(s) Vinnie Falco, Ville Voutilainen Target Audience WG21 Tracking issue View on GitHub Abstract For a detected core-language violation, the terminating response - invoke the handler, then terminate - is the default the evidence supports.
	P4318R0	Transient Benefit, Perpetual Cost: Implicit Core-Language Assertions	V. Falco	WG21
Intent Inform Mailing Date 2026-07 Post-Brno Author(s) Vinnie Falco Target Audience WG21 Tracking issue View on GitHub Abstract Standardizing a continuing (log-and-continue) response for implicit contract assertions on core-language undefined behavior, as a portable guarantee every implementation carries, returns less than it costs.

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

Mailings Beta

Sign in