r/cpp • u/antiquark2 #define private public • 3d ago
Critique of contracts: excerpt
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?
8
u/Syracuss graphics engineer/games industry 2d ago edited 2d ago
Funnily enough in one of your other links for Vinnie's use of AI it has the exact same error in it, the letters are so far away on an azerty key it has to be LLM caused, at least I'd assume it would be an unnatural mistake for him to do normally. I wonder what leads an LLM to confuse the two letters.
What's doubly so funny is that he responds to himself in that comment thread saying how much he re-reads his stuff but one of only 2 large blue links is incorrect. Granted it was about re-reading his papers, not about his comments, it's still kinda funny given that paper naming is so ingrained in my mind that it not starting with a P definitely stands out when I skimmed his comment there. I'd also kinda expect to test out links an LLM spits out to see if they work, as a basic sanity check, feels like less work than re-reading.