P3100 R5 Implicit contract assertions

[wg21bot]

P3100R0 Undefined and erroneous behaviour are contract violations (Timur Doumler, Gašper Ažman, Joshua Berne)

[wg21bot]

P3100R1 Undefined and erroneous behaviour are contract violations (Timur Doumler, Gašper Ažman, Joshua Berne)

[timuraudio]

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]

See #2186 as the follow up paper. I'm unclear if P3100 is still relevant, please update with a revision if so.

[wg21bot]

P3100R2 Implicit contract assertions (Timur Doumler, Joshua Berne)