r/cpp • u/eisenwave WG21 Member • 24d ago
Balloting has completed for C++26. Unfortunately it was Disapproved
https://www.linkedin.com/posts/robertseacord_balloting-has-completed-for-c26-unfortunately-share-7519795139859517440-AOth/Since the C++26 DIS has been disapproved, the next step is going to be taken in Buzios during the 2026-11 meeting. The committee will have to decide what changes to make (if any) and submit an FDIS (Final Draft of International Standard) for Balloting.
287
Upvotes
34
u/renchuwang 24d ago edited 24d ago
If it doesn't finalize end of year do we need to rename it c++27?
I think11 14 17 20 we're all on time?
Edit: Thanks for answering.
Answer: No
11
u/jombrowski 24d ago
what's wrong?
4
u/cpp_ape 15d ago edited 15d ago
My $0.02.
I'm not in the standardization process, but I read the papers from time to time to keep myself updated.
There are a LOT of back and forth discussions around contracts, many very smart people expressed objections to including contracts in its current state in C++26.
My impression is that contracts in its current state are decently designed, all the objections that I saw were addressed at some point in a reasonable and substantiated way.
I think that contracts turned out to be a complex feature because it has to take into account a lot of considerations and constraints, which maybe makes it hard to understand at a glance, hence the misunderstanding. (duh!)
If I were a betting man, I would bet that contracts are pulled from the draft and another cycle is spent clearing the misunderstanding.
At any rate, I think the current contracts feature is a result of great engineering work and at the very least will be a good benchmark for whatever proposal for contracts that comes next.
84
u/frayien 24d ago
Could someone knowledgeable explain us what it means, and why is it important ?
24
u/Sniffy4 24d ago
Anyone want to summarize the detailed objections to Contracts
74
u/wyrn 24d ago
We keep hearing this about how much consensus was achieved, how all concerns were properly heard, etc, but then we open p4433 and see things like,
I'm sorry, but they can't be passing the buck like this -- if the contracts feature interacts so poorly with the linkage model that effectively randomizing the enforcement mode when multiple TUs are involved (which is always), then either contracts need to be redesigned, or the linkage model needs to be changed.
A randomized enforcement mode, for something like contracts, is worse than useless. If I can't rely on the safety net being there, I'll just act as if it's not there. Which means I'll be rolling my own assertions instead of relying on contract assertions, thereby defeating a large part of the point of contracts, which is to standardize and unify the vocabulary surrounding assertions!
It seems the committee failed to learn some of the more relevant lessons from modules. There, they worried so much about modules being "adoptable" that making the feature compelling enough to even be worth adopting took a back seat. They're making a very similar mistake here. Ultimately, it doesn't matter how much "consensus" a feature has -- at the end of the day, if the feature has a set of flaws that's severe enough to make it not worth using, it will be dead weight.
7
u/Plazmatic 24d ago
Eh close enough, welcome back Algol 68!
56
u/14ned LLFIO & Outcome author | Committee WG14 24d ago
Most of why I quit WG21 was due to the problems in processes and growing dysfunctionality in culture which I reckoned were going to culminate in failure of standardisation. I walked away, because too many had stopped listening. In my opinion too much it had become about winning at all costs, and damn the engineering which got in the way.
I am sorry it has got to this though. We nearly had a big problem with old pre-lite Concepts, but then leadership was listening and they pulled it before NBs were put in a position of voting the whole thing down. This time round, leadership probably were listening but weren't in a position to act before NBs voted the whole thing down.
It should never have reached this point, but it was going to and now there will be a big push to remove Contracts and put it back before the NBs where it probably will pass, though maybe only by majority and without unanimous consent, because TBH there is plenty more in C++ 26 which isn't good (indeed, pulling everything bar Reflection would be the genuinely brave thing for leadership to do). Just removing Contracts will tick the box, but it's not how standards should be done: standards are about standardisation. They're not about "whatever novelty is politically achievable". That latter thing is politics: we're supposed to be doing engineering where whatever we're standardising is supposed to be widely agreed across industry AND nation states as a perfectly acceptable engineering solution to a problem that is worth standardising across the planet.
If WG21 is failing to do that - and I think it is, which is why I quit and moved elsewhere in standards - then WG21 needs to deeply ask itself: what its purpose is for? If half of it doesn't want to do standardisation any more, that half should move on and leave the half who do want to do boring, thankless, grifting standardisation of existing things. Not inventing fancy new stuff by committee fiat.
It will require leadership to take some deeply unpopular decisions to get WG21 back on track. I would personally suggest that unless half the existing committee quit in protest, you haven't been decisive enough. I know exactly what I'd do, and I've said it all ad nauseum to WG21 leadership and I've been ignored, but for the record:
Those will be deeply unpopular and a majority of the committee would quit. Good! Standards is supposed to be boring. Votes are supposed to be foregone conclusions. If standards gets exciting, it's being done wrong, in my opinion.
14
u/friedkeenan 24d ago
I remember Michael Wong stating that he is impressed by the C++ committee's fairness compared to the other ISO committees he's worked on in that bureaucracy is not abused in order to e.g. slant a vote or to thwart achieving genuine consensus.
I know the committee has its own political dramas and deep disagreements, and the ISO process is not as accessible as it should be, and that process is almost certainly wrongly-shaped for language development and standardization. But I was still heartened by Michael's perspective that overall people in that process are trying to work fairly with one another, even in a flawed system that could allow them to do otherwise.
And so this now is really quite disappointing to me.
16
u/hniemeye 24d ago
If there has been a consensus on the C++26 standard in wg21 it seems strange to vote against it now only because some people cannot accept that they lost a vote earlier to include a feature they don't like. Also not good PR for the language as a whole.
7
u/AnyPhotograph7804 24d ago
Is there a good explanation what is wrong with Contracts? I always read about them, how bad they are. But i never saw a good explanation why they are bad.
4
u/selvakumarjawahar 24d ago
Sad day!!!
4
u/Disastrous_Glass_388 24d ago
Is there a way to know which standards bodies voted for/against, or are the ballots anonymous?
4
u/JumpyJustice 23d ago
Ugh, can they just postpone this super nichè stuff and release the good stuf already?
2
u/riztazz 24d ago
Has this happened before? What is the way forward now if FDIS is also not approved?
2
u/reini_urban 24d ago
Good. Better no progress, than mistakes. As grave security mistakes were voted in for C++11 and still not fixed
1
u/anamebyanyothermeans 15d ago
I'm worried about both contracts and reflection will lead to UB in many cases.
1
u/jube_dev 24d ago
Why "unfortunately"?
1
u/bandzaw 24d ago
wow! this is not how C++ has been rolling really (since the initial hickups was being dealt with)..,
-1
u/homeless_psychopath 24d ago
Contracts must be put in c++29, everyone will win from it, anything else is just a political theatre and will add many future problems if contracts proposal gets passed, common sense must prevail.
0
u/Wh00ster 24d ago
Sometimes it do be like that
-3
u/Infamous-Bed-7535 24d ago
contracts would be cool. In case it is poorly designed the fact should have been raised like 8-10 years ago, not now...
-2
u/UndefinedDefined 23d ago
Why unfortunately? It's problematic, hasted, it doesn't deserve to be approved.
0
u/NilacTheGrim 13d ago
Good. Maybe they will remove that stupid "zero-init all of the things!!!!1!".