P2000R5 — Directions for ISO C++
(12 items)
All WG21
This paper articulates the long-term philosophy and operational principles guiding the evolution of C++, covering aims such as safety, simplicity, performance, and stability. It addresses process issues including proposal handling, trust within the committee, ABI stability, the role of technical specifications, and the balance of engineering tradeoffs. In R5, concrete short/medium-term priorities are moved to a separate paper (P5000), and new standalone directives on Profiles/Safety (P3970), AI strategy (P4023), and proposal convergence (P4024) are introduced and referenced.
- Section 5.2, page 15 — Cross-reference '(section 6.1)' points to 'The C++ Programmers Bill of Rights'; the Trust discussion it intends to reference is in section 5.1. [1] [1]
- Section 4 (Long-term Aims), page 5 — Citation key [Stroustrup,2018c] resolves to 'The Evils of Paradigms. P0176R0,' not to the Vasa paper. The correct key is [Stroustrup,2018b] ('Remember the Vasa! P0997R0'). [2]
- Section 2 (History) — In-text citation [Stroustrup2020] is missing a comma and does not match the bibliography key [Stroustrup,2020]; the citation will not resolve. [2] [3]
- Section 4 (Long-term Aims), page 5 — Citation [Winter,2016] has no corresponding entry in the references section. The closest match is [Winters,2017] (different surname, different year). [5] [4]
- Section 9 (References) — Document number 'N471' is not a valid WG21 number; the Networking TS document is likely N4711 or another 4+ digit number. The value appears truncated. [4] [5]
- Section 9 (References) — P????R0 is an unresolved placeholder paper number. [6]
- Section 5.1, page 12 — The paper states approximately 50 members 'back in 2025,' but it is dated 2026-02-23 and elsewhere claims over 500 meeting attendees (already true by 2022). The intended year is likely 1995 or another early standardization date. [7]
- Section 5.2 (page 15) vs. Section 5.2.1 (page 16) — P4024R0 is given two different titles: 'Guidance on Building Consensus and Converging Proposals' and 'Guidance on Converging on unified proposals.' One consistent title should be used. [8]
- Section 1 (Abstract), page 2 — The AI-related paper title appears as 'Directions for AI in C++' at one location but 'Strategic Direction for AI in C++: Governance, and Ecosystem' everywhere else; the plural/singular mismatch and missing comma should be reconciled. [9]
- Section 2 (History), page 3 — Spurious mid-sentence capitalization: 'Is' should be 'is.' [3] [10]
References — Anthropic Citations API
[1]
"the current 500+ membership of the C++ Standards Committee exceeds the largest estimates of Dunbar's number, in contrast to the roughly 50 committee members back in 2025."
"the current 500+ membership of the C++ Standards Committee exceeds the largest estimates of Dunbar's number, in contrast to the roughly 50 committee members back in 2025."
[2]
chars 41259–41890
"Remember the need for trust (§6.1): ● “I didn’t have time to read the document” is not sufficient reason to oppose (provided the paper was submitted on time) ● “I don’t understand” is not by..."
"Remember the need for trust (§6.1): ● “I didn’t have time to read the document” is not sufficient reason to oppose (provided the paper was submitted on time) ● “I don’t understand” is not by..."
[2]
chars 41259–41890
"Remember the need for trust (§6.1): ● “I didn’t have time to read the document” is not sufficient reason to oppose (provided the paper was submitted on time) ● “I don’t understand” is not by..."
"Remember the need for trust (§6.1): ● “I didn’t have time to read the document” is not sufficient reason to oppose (provided the paper was submitted on time) ● “I don’t understand” is not by..."
[3]
"the story of the Vasa, the beautiful 17th century battleship that sank on its maiden voyage because of (among other things) insufficient work on its foundation and excessive late additions..."
"the story of the Vasa, the beautiful 17th century battleship that sank on its maiden voyage because of (among other things) insufficient work on its foundation and excessive late additions..."
[4]
chars 5263–5452
"We strongly recommend that someone who wants to push or oppose a proposal read [Stroustrup,1994] and its related HOPL papers ([Stroustrup,1993], [Stroustrup,2007], and [Stroustrup2020]). "
"We strongly recommend that someone who wants to push or oppose a proposal read [Stroustrup,1994] and its related HOPL papers ([Stroustrup,1993], [Stroustrup,2007], and [Stroustrup2020]). "
[5]
"[Stroustrup,2022] B. Stroustrup and G. Dos Reis: Design Alternatives for Type-and-Resource Safe C++. P????R0. 2022-10-15."
"[Stroustrup,2022] B. Stroustrup and G. Dos Reis: Design Alternatives for Type-and-Resource Safe C++. P????R0. 2022-10-15."
[6]
chars 5029–5101
"Part of the reason for that Is that copies of D&E can be hard to find. "
"Part of the reason for that Is that copies of D&E can be hard to find. "
[7]
"P4024R0: Guidance on Building Consensus and Converging Proposals. / added pointer to P4024r0:Guidance on Converging on unified proposals"
"P4024R0: Guidance on Building Consensus and Converging Proposals. / added pointer to P4024r0:Guidance on Converging on unified proposals"
[8]
"P4023R0 (Strategic Directions for AI in C++: Governance and Ecosystem). / P4023R0: Strategic Direction for AI in C++"
"P4023R0 (Strategic Directions for AI in C++: Governance and Ecosystem). / P4023R0: Strategic Direction for AI in C++"
[9]
chars 72255–72335
"● [Wakely,2017] Jonathan Wakely: Extensions for Networking. N471. 2017-11-27. "
"● [Wakely,2017] Jonathan Wakely: Extensions for Networking. N471. 2017-11-27. "
[10]
chars 10627–10815
"Changing parts deemed insignificant can be risky (we need better analysis tools [Winter,2016]) 5 Directions for ISO C++ DG P2000R5 and the potential gains would be insignificant. "
"Changing parts deemed insignificant can be risky (we need better analysis tools [Winter,2016]) 5 Directions for ISO C++ DG P2000R5 and the potential gains would be insignificant. "
Summary: P2000R5 is a standing document that articulates the committee's long-term design goals, priorities, and process guidelines for the evolution of ISO C++. It covers historical context, overarching principles (type safety, performance, teachability), specific technical directions (e.g., static analysis, modules, concurrency), and procedural guidance for how proposals should be evaluated.
Pipeline: Discovery (Anthropic Opus + Citations API) → Verification Gate (OpenRouter Opus) → Report Writer (OpenRouter Opus)
Provenance: All references are machine-verified character positions from the Anthropic Citations API — deterministic, exact substrings, not model-generated quotes.
Provenance: All references are machine-verified character positions from the Anthropic Citations API — deterministic, exact substrings, not model-generated quotes.