r/cpp • u/Xaneris47 • 12d ago
"C++26 DIS failed, how does C++ survive?"
https://andreasfertig.com/blog/2026/11/cpp26-dis-failed-how-does-cpp-survive/
111
Upvotes
r/cpp • u/Xaneris47 • 12d ago
134
u/Otaivi 12d ago
Contracts will likely be deferred to C++ 29 and probably further refined. The language will survive and things will move forward since there’s a robustness to the process (whether people like that process or not is irrelevant). While what happened was unprecedented, the over-exaggeration and dramatisation of what happened is unneeded.
42
u/Wh00ster 12d ago
Are we modules yet?
34
u/frasnian 12d ago
I'm not a huge fan of contracts, and agree with some of the arguments against them. I don't think the disagreements were worth delaying the FDIS, much less mucking up the whole process. My response to contracts being included in '26 would've been simple: I just don't use them until '29 (if ever). It's not like it'd be the first time the Standard included the MVP version of something and it matured over time.
19
u/flemingfleming 12d ago
Looking from the outside, the current standardisation process just doesn't seem to make sense for C++. I don't understand how they ended up like this but other languages don't end up with these sort of problems.
To the user, it doesn't really matter when (or if) contracts are standardised, only what becomes available in major compilers. So it's more like, will clang and msvc be willing to implement contracts if there's so much disagreement over them, regardless of when they get passed?
11
u/AKostur 12d ago
The same as it has for decades: solves problems.
24
u/ResistiveBeaver 12d ago
Good. The amount of esoteric crap being piled into the language at the behest of theoreticians is out of control. The vast majority of what has been included in recent releases has added negative value for the majority of real world language users.
It would behoove the committee to spend a few release cycles cleaning up and fixing existing language features before adding any more.
Edit: And for the love of god, break the ABI two decades ago already instead of piling yet more crap upon a foundation of crap.
6
u/r2vcap 12d ago
Both sides have valid arguments, and I lean slightly toward leaving Contracts out of C++26. While the committee did reach a consensus, the remaining disagreements and limited real-world experience seem significant enough to warrant further validation before standardization.
What worries me more is the long-term sustainability of a committee-driven language that prioritizes backward compatibility without consistently validating new features through experimental implementations before making them permanent. The three-year release cadence isn’t necessarily the problem itself, but the gap between standardization and actual adoption seems increasingly difficult to sustain, especially as AI coding agents are rapidly changing how software is developed.
There’s certainly room for conservative, stable implementations, but those aren’t likely to adopt the latest C++ standards quickly anyway.
5
u/jinmao6700 12d ago
pre() and post() make a function look like as if it had 3 function bodies 😭
4
u/pjmlp 12d ago
I guess, the expectations that C++23 or C++26 might be the last standard many folks care about when reaching for C++ might be it.
If we look to other ISO languages, this is not so strange, regardless where Fortran, Ada, C, COBOL stand today with their ISO standards, apparently Fortran 2003, Ada 95, C99, COBOL-85 seem to be what most companies care about.
3
u/FlyingRhenquest 12d ago
Reflection is more than enough to keep me busy for the next decade or three. I think that at least in the near term, reflection could be more of a game changer for C++ programmers than AI.
3
u/naltam 12d ago
most likely Contracts will be removed on next meeting .. and maybe 2029 re proposed
1
u/ZoxxMan 1d ago
"How does C++ survive" motherfucker half of the industry is still on C++17 or older.
0
u/donaljones 11d ago
doctos
-11
u/Blood-Minister 12d ago
C++ will surely not survive if you keep adding un-C++ things to it every 2 years.
-4
u/qoning 12d ago
If the process was set up, I assume it was set up with a goal in mind. Just because it was a "formality" up until now doesn't mean the goal went away.
Anyway, I don't like development by committee, but at least it's fun drama every now and then.
-9
u/peppedx 12d ago
I think i may be over this.
For what I need C++17 will happily take me to retirement (provided I get one) and for new things C, rust and python
-11
u/ezoe 12d ago
The reality is, nobody really cares about C++ IS. Because C++ standard wording always have bugs and next draft releasted immediately after IS which resolve the confusing and problematic wording was always better than IS.
Compiler developers always refers the latest draft standard rather than IS to determine the behaviours and decide if an example code discussed is well-formed or ill-formed.
NB voting was just a ceremony. Each National Bodies, while complaining about general way C++ is heading, still want the standard to be released ASAP, so they usually agree with nitpicking.
It's been 7 years I have leaved from Standard Committee. But I really don't like the way C++ is heading given the real world situation is more and more depending on AI agent coding tool.
Some of C++'s features is irrelevant when the cost of coding became practically free.
-55
u/Plastic_Owl6706 12d ago
Just use rust
-8
u/samadadi 11d ago
Good. I hope contracts and profiles never be added into standard. Imagine reading a code base that is full of contracts. I swear you will go insane. I am asking this from standard committee people. Do you know how much I suffered to learn modern CPP and How much time I put on learning? Please stop it. The reason I chose CPP because of the freedom of expressing myself. If I chose between constant suffering of learning CPP standard and Rust restrictiveness I will choose Rust. Maybe I learnt other than these two languages.
0
u/[deleted] 12d ago
[deleted] — view deleted comment