You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
P3100 R9 A framework for systematically addressing undefined behaviour in the C++ Standard #1901
changed the title [-]P3100 R0 Undefined and erroneous behaviour are contract violations[/-][+]P3100 R1 Undefined and erroneous behaviour are contract violations[/+]on Oct 17, 2024
Seen by SG21 in Wroclaw. 2024-11-22. The following polls were taken:
Poll 6.
We support the direction of P3100R1 and encourage the authors to come back with a fully specified proposal.
SF F N A SA
19 6 0 0 0
Result: Consensus
Poll 7.
We want to see a paper, targeting C++26, that removes the allowance for erroneous behaviour to terminate execution at an unspecified time after the erroneous operation rather than immediately, thus making the allowed set of behaviours a strict subset of the evaluation semantics proposed in P3100R1.
SF F N A SA
4 10 4 2 1
Result: Consensus
Poll 8.
We want to see a paper, targeting C++26, that allows erroneous behaviour to call the contract-violation handler.
changed the title [-]P3100 R5 Implicit contract assertions[/-][+]P3100 R5 A framework for systematically addressing undefined behaviour in the C++ Standard[/+]on Mar 19, 2026
EWG saw this in Croydon on Thursday afternoon and took the following polls:
Forward P3100R5, with the presented rules applied to UB in the standard, to CWG for inclusion in C++29
SF
F
N
A
SA
1
17
10
18
14
not consensus
Update P3100R5 by applying the presented rules to all cases of runtime-checkable UB in the standard, as listed in appendix A, and bring it back to EWG for case-by-case wording review
changed the title [-]P3100 R5 A framework for systematically addressing undefined behaviour in the C++ Standard[/-][+]P3100 R6 A framework for systematically addressing undefined behaviour in the C++ Standard[/+]on May 12, 2026
changed the title [-]P3100 R6 A framework for systematically addressing undefined behaviour in the C++ Standard[/-][+]P3100 R7 A framework for systematically addressing undefined behaviour in the C++ Standard[/+]on Jul 17, 2026
Temperature poll during EWG 2026-07-27 teleconference.
P3100R7/D4277R0: EWG is no longer interested in continuing our case-by-case review of Undefined Behavior from P3100 in telecons, and thus will stop our review in telecons
changed the title [-]P3100 R7 A framework for systematically addressing undefined behaviour in the C++ Standard[/-][+]P3100 R8 A framework for systematically addressing undefined behaviour in the C++ Standard[/+]on Aug 15, 2026
changed the title [-]P3100 R8 A framework for systematically addressing undefined behaviour in the C++ Standard[/-][+]P3100 R9 A framework for systematically addressing undefined behaviour in the C++ Standard[/+]on Oct 26, 2026
Activity
wg21bot commentedon Oct 17, 2024
P3100R1 Undefined and erroneous behaviour are contract violations (Timur Doumler, Gašper Ažman, Joshua Berne)
[-]P3100 R0 Undefined and erroneous behaviour are contract violations[/-][+]P3100 R1 Undefined and erroneous behaviour are contract violations[/+]timuraudio commentedon Dec 9, 2024
Seen by SG21 in Wroclaw. 2024-11-22. The following polls were taken:
Poll 6.
We support the direction of P3100R1 and encourage the authors to come back with a fully specified proposal.
SF F N A SA
19 6 0 0 0
Result: Consensus
Poll 7.
We want to see a paper, targeting C++26, that removes the allowance for erroneous behaviour to terminate execution at an unspecified time after the erroneous operation rather than immediately, thus making the allowed set of behaviours a strict subset of the evaluation semantics proposed in P3100R1.
SF F N A SA
4 10 4 2 1
Result: Consensus
Poll 8.
We want to see a paper, targeting C++26, that allows erroneous behaviour to call the contract-violation handler.
SF F N A SA
11 7 4 1 0
Result: Consensus
jfbastien commentedon Feb 12, 2025
See #2186 as the follow up paper. I'm unclear if P3100 is still relevant, please update with a revision if so.
wg21bot commentedon May 20, 2025
P3100R2 Implicit contract assertions (Timur Doumler, Joshua Berne)
17 remaining items
hanickadot commentedon Mar 11, 2026
EWG won't see any contract paper targeting 29 at Croydon in order to focus on contracts in 26.
[-]P3100 R5 Implicit contract assertions[/-][+]P3100 R5 A framework for systematically addressing undefined behaviour in the C++ Standard[/+]je4d commentedon Mar 26, 2026
EWG saw this in Croydon on Thursday afternoon and took the following polls:
Forward P3100R5, with the presented rules applied to UB in the standard, to CWG for inclusion in C++29
not consensus
Update P3100R5 by applying the presented rules to all cases of runtime-checkable UB in the standard, as listed in appendix A, and bring it back to EWG for case-by-case wording review
strong consensus
wg21bot commentedon May 12, 2026
P3100R6 A framework for systematically addressing undefined behaviour in the C++ Standard (Timur Doumler, Joshua Berne)
[-]P3100 R5 A framework for systematically addressing undefined behaviour in the C++ Standard[/-][+]P3100 R6 A framework for systematically addressing undefined behaviour in the C++ Standard[/+]hanickadot commentedon Jun 10, 2026
EWG in Brno on Wednesday:
Result: consensus
wg21bot commentedon Jul 17, 2026
P3100R7 A framework for systematically addressing undefined behaviour in the C++ Standard (Timur Doumler, Joshua Berne)
[-]P3100 R6 A framework for systematically addressing undefined behaviour in the C++ Standard[/-][+]P3100 R7 A framework for systematically addressing undefined behaviour in the C++ Standard[/+]hanickadot commentedon Jul 27, 2026
Temperature poll during EWG 2026-07-27 teleconference.
Result: not consensus
wg21bot commentedon Aug 15, 2026
P3100R8 A framework for systematically addressing undefined behaviour in the C++ Standard (Timur Doumler, Joshua Berne)
[-]P3100 R7 A framework for systematically addressing undefined behaviour in the C++ Standard[/-][+]P3100 R8 A framework for systematically addressing undefined behaviour in the C++ Standard[/+]wg21bot commentedon Oct 26, 2026
P3100R9 A framework for systematically addressing undefined behaviour in the C++ Standard (Timur Doumler, Joshua Berne)
[-]P3100 R8 A framework for systematically addressing undefined behaviour in the C++ Standard[/-][+]P3100 R9 A framework for systematically addressing undefined behaviour in the C++ Standard[/+]