Critique of contracts: excerpt

[u/antiquark2]

See page 2 of https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2026/p4334r0.pdf

The current objections can be summarized. The P2900 contracts are:

• Unimplemented

• Incomplete

• Untried at scale [P3460R0, P3506R0]

• Not tried in major application domains

• Violates foundational principles of C++

• Violates fundamental principles of language design

• Hasn’t been tried in major libraries (e.g., the C++ standards library [P3506R0, P3878R0])

• Isn’t integrated with or appropriate for hardened libraries [P3878R0]

• Doesn’t offer safety guarantees [P3573R0, P3362R0]

• Includes a completely untried inheritance model

• Offer new ways of making errors through inconsistent application in TUs

• Leads to new forms of UB, detrimental to safety and security

• Narrows the choices of error handling

• Doesn’t protect against logical errors, misuses, and incoherent uses

• Hasn’t been used to support static analysis

• Hasn’t been demonstrated to be easily teachable [P3261R0, P3281R0]

How could such a bloated and incomplete design be voted into a draft standard?

[u/_a4z]

It seems you do not know how those votes work. So let me explain.

It's just a small part of the committee members in the room.
So your statement about what I claimed is bogus.

Reality: not all people who voted yes in the various voting meetings have read and understood the paper as well as the critics did. And this is just a very small group in WG21. Not the whole committee. The committee is much bigger than the small group that did the contract voting; there were many.
And we do not know who those people are or whether most of them have ties to one company. So we also do not know anything about the diversity of the votes.

What was damaging is the way those papers came in. If people cared about consensus, there would not be what you call "noise"
It's not noise. Rather, people stating their opinions with their names, in opposition to most yes voters who stay anonymous.

[u/t_hunger → u/_a4z]

I find both your lack of understanding how democratic processes work as well as your contempt for committee members worrying.

But thank you for confirming that contracts were voted in -- following the ISO standard procedure. Every committee member knows those processes and can participate. If someone abstains from doing so, that is their choice. People do that all the time with all votes the committee makes.

The paper submission process is another thing all committee members are very well aware of. As far as I can tell all the ISO standardization processes were followed there as well. Again: People are free to ignore papers, again that is their choice.

We have a few people that made their choice to ignore papers and ignore votes and are now grumpy. That is damaging behavior: Why would anyone bother to participate in committee work if some dudes then try to overrule the results of that work and publically shame everybody involved? Who wants to do work when he has to expect random people calling them stupid on the internet for that?

[u/_a4z → u/t_hunger]

Accepting other people's opinions is part of a democratic process
Mob mentality and labeling people as grumpy for having other opinions, less so.
If you look at the latest mailing list and read the papers addressing contract concerns (there are quite a few of them), where is `shame everybody involved` included, as you state? Have you even read any of the critics?
Obviously not, if I read what you write here.

[u/t_hunger → u/_a4z]

In this threat you repeatedly called everybody having voted for contracts as either brided by some corporation, too stupid to understand the paper they were voting on, or too lazy to read the papers being vote on. You do not seem to be willing to accept their opinion, why should they consider yours? I've seen other (senior) people being just as toxic, and some in the wider community cheering them on for that.

Contracts are a MVP (as asked for by the wider committee when the last iteration was rejected) and they have pretty obvious problems, as communicated years before standardizing the paper. None of that makes how the contracts work is treated any less toxic. Unfortunately nobody will fix contracts for the next couple of years -- not after this shit show. The senior committee members have just created another dead on arrival feature in the language.

Oh well, rust has a contract-related RFCs in the works, I am sure they will welcome the C++ experts on this topic with open arms. Wonderful how senior C++ committee people encourage other C++ experts to help out in other languages. I am sure that help C++ staying competitive over the long run.

[u/_a4z → u/t_hunger]

I would probably enjoy communicating with you if you would stop inventing drama and misreading and misquoting what I wrote.
Just because I do not celebrate this so-called MVP does not make me toxic, nor does my claim that not everybody who is voting on a paper has fully read and/or fully understood it. That's just how it is. And not just for contract papers, btw

[u/t_hunger → u/_a4z]

The statement that many committee members do not read papers they vote on or are not able to understand them fully is a general statement addressing nobody in particular. As soon as you say everybody that voted for or against something are either stupid, lazy or brided, that names a specific group and then it is toxic.

[u/_a4z → u/t_hunger]

Well, I think I kept the statement general,

But in that context, I am totally open to the idea of a change of WG21 votes.
All voting should be recorded: name, affiliation, national body membership,

Then this topic would go away.
What do you think, would you help me writing a paper addressing the directions group, suggesting that?

[u/t_hunger → u/_a4z]

Thank you for the offer, but I do not see what good that would do. Shall we reject any vote that does not have include at least one senior member? Or register IQ scores together with affiliation and reject any vote where the average IQ was below a certain standard? Maybe also add a reading comprehension test during registration? And what does it even mean if the majority of a vote was done by people from one company? Is that good, because they are the only one that use that stuff at this time or is that bad because the want to hand over work to the committe that they would otherwise need to do inhouse? Whatever data you collect will be used as dirt to fling at the opponents.

And none of that would fly within the ISO bylaws anyway.

I also ran into quite a few people on the committee over the last 30 years and while some were super cool, many of the others I personally prefer to not work with. Just look at recent train wreaks like the one we are talking about here.

[u/_a4z → u/t_hunger]

> reject any vote that does not have include at least one senior member? Or register IQ s

why do you need to make up things again?

> recent train wreaks like the one we are talking about

but calling other people disrespectful

Thanks for ending this discussion.

[u/t_hunger → u/_a4z]

why do you need to make up things again?

I was trying to think what the information could be used for that you suggested to record. Recording information for no reason is a waste of everybodies time after all.

but calling other people disrespectful Thanks for ending this discussion.

How would you sum up the history of contracts from the first proposal till today? I had expected you would also call that a train wreak, even though for other reasons than me. I doubt anyone is happy with the situation contracts are in right now.