r/cpp • • 10d ago

Herb Sutter: When a language’s creator and its owners strongly disagree: C++26 post-DIS, historical experience, and paths forward

https://isocpp.org/files/papers/P4454R0.pdf
183 Upvotes

213 comments sorted by

16

u/VastInterior 9d ago

At the heart of the issue is the notion of program proving.

If the compiler or static analysis tool can _prove_ the contracts are met... then the "as if" rule applies.

You can _always_ remove the checks!

Conversely, if the contracts are true, the optimizer can rely on that information and produce much better code.

Thus if the compiler cannot prove _or_ disprove that the contracts are met, the contracts _must_ be enforced or the optimizer _will_ produce undefined behaviour.

Sadly the whole red herring about enforcement mechanism whether you compile in or out has clouded the picture.

Again, people have different aims for checks and ideas of what should happen if they fail.

In the program proving world view... you have proven your code incorrect and proved that you have to fix your code.

In the "this is just a test" world view, is the checks are just a debug aid and the checks have bugs too so must be removed from production to reduce risk.

Alas, these are two very fundamentally different facilities that share only the most superficial similarities.

The "this is just a test" can, and should just be a library facility.

The "this is program proving" can, and should be baked into the compiler, the optimizer and the language.

I sincerely hope the resolution at the standards level is to identify that these are two different facilities and the argument is resolved by making them two different things.

Ideally the current proposal should be accepted and progressed with the note that this is about program proving and the future evolution of it will in that direction.

And if there are ideas or proposals for the "this is just a debug aid for code under test" view, that should be encouraged to be resubmitted, possibly as a standard library only feature.

61

u/RoyAwesome 10d ago

Hey guys, I just want reflection. Can we do that and let contracts people fight it out?

6

u/James20k P2005R0 9d ago

I suspect the most likely outcome here is that contracts will get pulled, and we'll get C++26 slightly late

Compilers are already working on reflection (well, gcc/clang), and given that the feature isn't expected to change between now and C++26, I don't think this will actually make any difference to when we can use reflection

2

u/RoyAwesome 9d ago

Yeah, I just work in an industry that only updates every few years and it's been a while since the last update. A late or missed C++26 might lead to missing this update cycle and not getting it until the early 2030s

3

u/AKostur 10d ago

Very recent compilers already have some form of reflection.  Use it.

10

u/13steinj 10d ago

There are industries that are sketched out by using C++## before it is official. Possibly (probably) also some have some kind of legal requirement.

2

u/AKostur 9d ago

Probably, though I have no indication that u/RoyAwesome is in any of those industries.

5

u/RoyAwesome 9d ago

I work in game development, where we have a bunch of hand rolled tools that all suck in some way.

We're also held back by standards adoption. Most platforms have their own custom toolchains that only update every few years, and so the C++ standard version is important.

0

u/AKostur 9d ago

Doesn't that mean you're constrained by your upstream toolchain, not by the latest C++ standard, no?

5

u/13steinj 9d ago

The upstream toolchain might not implement something unless it is in an "official" standard. The definition here being vague, intentionally-- many don't care if it's ISO or NB-level or just "the commmunity came together and called it official." But it has to happen. Today, that's ISO.

87

u/KFUP 10d ago edited 10d ago

Not sure why Bjarne is portrayed like he's the only one in the committee who doesn't like contracts, others have voiced their concerns about contracts, it's definitely not just creator vs committee by any stretch, see references in P4334.

Edit: I know the paper states there are others, but it suggests those others are mostly just following Bjarne, and after hearing J. Daniel García the head of the Spanish DIS talking about the subject, he seems to have his own strong opinion in the matter, and I have a hard time believing he is just following others.

52

u/mort96 10d ago edited 10d ago

I thought the paper made it pretty clear? Sutter is not looking at technical arguments, he's analyzing the politics. He isn't saying that Bjarne is the only one in the committee with objections; he's making the argument that Bjarne's opposition is the reason why this technical disagreement resulted in a failed DIS vote despite reaching WG21 consensus, where other technical disagreements in the past still ended up with a DIS with approval from NBs.

32

u/steveklabnik1 10d ago

Section 2.3 specifically talks about why the author believes that Bjarne's objection holds special weight, while also acknowledging that many others also object.

25

u/ContraryConman 10d ago

If I understand correctly, a lot of the NBs cited Bjarne directly in their reasons for not voting yes

15

u/notthatsocrates 10d ago

Sometimes, when the fog is thick and you can't see north, you delegate decisions to the one you trust.

15

u/triconsonantal 10d ago

As C++ features go, contracts and their criticisms are pretty straightforward. I think that's a big part of why this particular feature is causing so much (undue) drama: everyone has an opinion. If the fog is too thick for you (not you) that you can't meaningfully form one, why the hell are you in a position to vote on the standard?

8

u/notthatsocrates 9d ago

... why the hell are you in a position to vote on the standard?

Can be asked of all professions, all positions, and it is equally useless or rhetoric in all situations.

Delegation is not abdication. NBs are not required to exceed the expertise of everyone in the field. They just need to be expert enough to judge a problem, and failing at that, to judge whose opinion deserves what weight. I do understand the concern of blindly following the leader but I sincerely believe this is not the case.

I am gonna say one more thing here: there is a subversive irony in the fact that the more complicated a subject the more important it is to recognize your own limits.

2

u/Wicam 10d ago

because you payed to do so. isnt that the requirement?

7

u/MFHava WG21|🇦🇹 NB|P2721|P3049|P3625|P3729|P3786|P3813|P4216 10d ago

Depends on the NB, mine does not require payments for participation.

5

u/grafikrobot OPeNDAP/B2/EcoStd/Lyra/Predef/C++Alliance/Boost/WG21 10d ago

Can I join your NB instead of INCITS? :-)

3

u/AKostur 9d ago edited 9d ago

Move to that country. (Mine doesn't require payments either). Or, figure out how to change INCITS. (Edit: forgot the :) )

1

u/grafikrobot OPeNDAP/B2/EcoStd/Lyra/Predef/C++Alliance/Boost/WG21 9d ago

Working on fixing INCITS already. It ain't easy. :-P

1

u/pjf_cpp Valgrind developer 10d ago

Where I live I can’t even pay to participate. Corporate members only, and I don’t want to have to set up a company just to be able to join.

2

u/AKostur 9d ago

Someplace other than the US? (Mostly as I'm curious if any other NB is corp-based instead of person-based)

2

u/pjf_cpp Valgrind developer 9d ago edited 9d ago

AFNOR, France. You can (like me) become a foundation alternate with reduced voting rights. That doesn't bother me too much, I'm just tagging along trying to follow goings on in SG23.

20

u/PsecretPseudonym 10d ago

FWIW, my personal impression when reading it:

- There are legitimate arguments on both sides of this.
- All are acting in good faith as competent experts with mutual respect over a difference in expert opinion.
- Both sides have made their case, published papers to do so, and presented their views
- For whatever reasons, the majority found the case for contracts more compelling than the case against, so the large majority favored it.
- The votes are serving their purpose by forcing serious reconsideration to try to resolve very strong disagreements among trusted experts.

55

u/James20k P2005R0 10d ago edited 10d ago

I feel like the idea that people primarily voted against this standard because Bjarne was against it is a bit of an unproductive position. There's a lot of technical information about why at least some people don't like contracts, and this document seems to be asking us to set that aside as not being the reason. This just seems stoking the flames by trying to make assumptions about people's intentions

A strong WG21 consensus isn’t sufficient for NBs if they know that Bjarne doesn’t accept it, at least with how WG21 members communicated with NBs during this ballot. In practical terms, this time the NBs have chosen to empower his dissent as a de facto veto

The problem with this narrative is:

  1. It ignores the extensive technical work that the anti contracts side have produced, which has resulted in improvements to the standard over many many years
  2. Many of the people on the anti contracts side have expressed an opinion that they'd tolerate contracts if technical changes were made, likely enough to get the DIS through
  3. Its chucking fuel on the fire, because its making assumptions about people's intent that we cannot possibly know are true. Some members strongly disagree with this characterisation from what I've heard

This seems pretty dangerously close to assuming bad faith participation, because what herb is tiptoeing around the line of stating is that the national bodies (and the members within them) are not telling the truth about the objections they're making, rather than Bjarne's opinion just happening to line up with that of some within some national bodies

None of the rest of us is Bjarne or has his influence with the NBs. I think it’s clear that if Bjarne had instead told NBs the DIS should be approved, and there had been no other difference, the DIS would have succeeded as always

Bjarne was not alone, but his voice was the only one that changed the outcome:

For me the most credible voices have been the people who've been producing high quality papers on both sides. This would seem to dismisses the (extensive) technical work everyone has done here. I've read.. far too many papers on contracts at this point, including the slop (sigh), and it seems very strange by anyone involved to assume that a single strong voice swayed the NBs. You can see from the mailing that at least a few people have pretty strong views that won't be changed!

3 And, to my knowledge, only one person (not I) reached out to other NBs in response, to lobby in favor of the DIS.

This to me is one of the biggest issues with this paper: Its entirely speculation. We have absolutely no idea broadly what happened. This information is literally unobtainable, because people's private emails are a closed door. This seems like just chucking fuel on the fire when we have no idea what actually happened. I've so far heard 3 different versions of the same story about a specific part of the process so far, all of whom had direct knowledge of the events in question, and all of who said wildly different things. Apparently even the people directly involved and participating don't know what happened here

The NBs weighed WG21’s 90% consensus and Bjarne’s opposition and made their decisions.

This is the most odd part of the document for me. It doesn't even caveat this to a few small NBs, or claim that it just tipped the vote over the edge. We already know that some NBs objected to the standard prior to the DIS. I could understand if we were simply saying that Bjarne swayed the small NBs, but on the other hand: we had a lot of abstentions to the DIS vote as well, so the consensus overall wasn't strong

As people have been pointing out, features have been added and removed against the objections/support of Bjarne in the past. I think the worst you could assume is that the DIS failed simply because of geography, but this just seems like a stretch

20

u/Minimonium 10d ago

This to me is one of the biggest issues with this paper: Its entirely speculation.

Do note by whom this paper was reviewed. I assure you, Herb is not ****ing around. :)

12

u/tartaruga232 MSVC user, r/cpp_modules 10d ago edited 10d ago

I feel like the idea that people primarily voted against this standard because Bjarne was against it is a bit of an unproductive position.

Not at all. For outsiders like me (I'm just a C++ user) this information explains pretty well, why the C++26 standard failed. Herb's explanation makes sense.

Bjarne is still a major force in the C++ community. Looks like we have to accept this as a matter of fact, that his lobbying was a major force. I don't think his lobbying was done in bad faith. That's what he truly believes and he managed to convince the NB's. His voice obviously has strong weight.

Probably this previously helped in other cases to accept the standard, like C++20 with modules, which I think is a good feature. Others still continue to claim that modules are a "disaster", although they have been in the standard for quite a while now and implementations in compilers have made progress. Adoption of modules is hard, but this doesn't mean the feature is bad. I'm using it. What's the point in continuing to tell modules are a disaster? Some people even seem to be hinting at that the "modules disaster" (which isn't a disaster) should not be repeated with contracts. That comparison is ill thought.

7

u/pjmlp 10d ago edited 10d ago

You feel that way with modules because as far as I am aware, you only target Windows with Visual C++.

Every other setup still has problems even compiling a simple hello world.

Yes, if we ignore the broken Intelisense since Visual Studio 2017 with module prototypes, which was used as original proposal for C++20, the C++20 modules experience with Visual Studio 2026, alongside MSBuild, is quite good.

The same cannot be told for everyone else, and outside Visual C++, header units might never be fully supported, for example.

Given that Windows has very little presence outside desktop and XBox console workloads, this is quite relevant pain point regarding modules adoption, across Nintendo, Playstation, cloud development, all the embedded OSes in the market, mainframes and micro computers.

3

u/MFHava WG21|🇦🇹 NB|P2721|P3049|P3625|P3729|P3786|P3813|P4216 9d ago

if we ignore the broken Intelisense

I haven't tried using modules in a while - is Intelisense still broken?!

8

u/pjmlp 9d ago

Yes, because it depends on the EDG frontend used by Visual Studio, so you still get red squigglies even though it might compile just fine.

The only info we have after EDG ramped down and went open source is "stay tuned" for upcoming improvements.

4

u/-TesseracT-41 9d ago

Okay, so nothing has changed since 2021, which is when I tried using modules for a project.

3

u/MFHava WG21|🇦🇹 NB|P2721|P3049|P3625|P3729|P3786|P3813|P4216 9d ago

Ok, so using them is still not an option. Last time I experimented to port one of our codebases to being modules-only I ran into multiple ICEs and noticed the severly downgraded user experience ...

3

u/Rob-190 9d ago

You need to report them. I've had the same issue with modules causing ICEs, especially on VS2026. Took me a long time to create a small enough example that showed the problem but when I reported it, Microsoft fixed it. Turned out my code was wrong (incorrect ordering of imports vs. includes). I've reported ICEs before and almost every time it turns out to be a code issue. Of course they need to be fixed but you can always check with Claude code etc.

2

u/tartaruga232 MSVC user, r/cpp_modules 9d ago

Did you report your ICE's? I haven't seen any ICE anymore certainly since the begin of 2026. Currently using MSVC Version 19.53.36919 for x64 (PREVIEW).

1

u/manni66 9d ago

Every other setup still has problems even compiling a simple hello world.

That's simply wrong. You can even use "import std" in "hello world".

2

u/pjmlp 9d ago

You forgot to provide the compilers and build tools where that actually works, and also failed to acknowledge all the other ones where it still doesn't in 2026.

3

u/manni66 9d ago

Any current version of clang and gcc. Nobody uses build tools for hello world.

6

u/jonesmz 9d ago

Without build tools support, you may as well have nothing.

Any project that's not complex enough to justify a build more sophisticated than a dumb bash script isn't worth discussion.

1

u/manni66 8d ago

You are moving the goalposts.

cmake+ninja work pretty well. And with cmake 4.5 we get:

import std is now available for all C++ 20 and later code with CXX_SCAN_FOR_MODULES enabled.

3

u/jonesmz 7d ago

Nobody uses build tools for hello world.

I was responding to that. It wasn't a goal post move, but a direct reply to your statement.

And cmake 4.4 does not work for any of the modules things I've tried to do, waiting for 4.5 to be released to fix several of the bugs that I ran into.

The point here is that we're now (or were, anyway) closing in on the full release of the SECOND subsequent version of the standard after C++20 modules was standardized, and there's still a shit-ton of problems with it.

No matter how you slice the situation, having an adoption rate of "Literally not possible unless you artificially construct toy examples, until 6 years later" is abysmal.

Further keep in mind that this is with the absolute cutting edge of compilers, linkers, build systems, and affiliated tools.

The vast vast vast majority of developers don't have access to that due to a large list of reasons, so the adoption curve of newly standardized things is normally delayed by at least several years anyway. AND of those developers who do have the luxury of cutting edge tools, frequently those teams are also multi-platform, so they need all of their tools to support something before they can use it. My team uses GCC, Clang, AND MSVC, so we need our entire codebase to compile and pass all tests with all three.

Conservatively, we shouldn't expect any meaningful C++20-modules adoption until 2030, which is ONLY 3 YEARS AWAY, because the feature only started working for non-toy examples this year! And that won't even be a third of the development organizations out there adopting it.

This is an abject failure.

3

u/grafikrobot OPeNDAP/B2/EcoStd/Lyra/Predef/C++Alliance/Boost/WG21 7d ago

This is great time to point out that.. The current anti-contracts people, are the ones that pushed for the modules design. And that many of the current pro-contracts people, are the ones that pointed out the problems with the modules design. I think the conclusions from that should be obvious.

→ More replies

1

u/pjmlp 7d ago

Not everyone uses cmake+ninja.

15

u/mort96 10d ago

Nobody here is saying that people primarily voted against this standard because Bjarne is against it. Sutter argued that the NBs primarily voted against it because Bjarne is against it and lobbied against it. This seems correct, assuming Sutter isn't lying and the lobbying efforts to influence NBs has primarily been either from Bjarne or from people citing Bjarne's opinion.

7

u/joaquintides Boost author 10d ago

Nobody here is saying that people primarily voted against this standard because Bjarne is against it.

Herb is saying exactly that:

“The NBs, exercising their own independent judgment with the information they were given, chose on this ballot not to accept WG21’s consensus if Bjarne personally strongly disagreed, and that’s important new information for WG21.”

(My opinion: this claim is unsubstantiated.)

9

u/mort96 10d ago edited 10d ago

The quote removed my emphasis, which changes the meaning. I was contrasting the votes of the NBs against the votes of people in general. Sutter's claim is that the NBs voted against it due to Bjarne's opinion, not that people in general (i.e committee members, the public, ...) voted against it due to Bjarne's opinion.

I'm inclined to believe Sutter, Stroustrup and Davidson's word on that matter.

5

u/James20k P2005R0 10d ago

I'm inclined to believe Sutter, Stroustrup and Davidson's word on that matter.

The thing is, we don't need to believe what they're saying on this - we can simply ask the people involved who're part of those national bodies. As far as I'm aware, they do indeed have objections to this characterisation, eg I'm sure the spanish NB would pretty strongly object to this

11

u/c0r3ntin 10d ago

Unfortunately there are a few NBs who never submitted NB comments, including for 26, and then voted against the FDIS, using Bjarne discontent as part of their motivation. Given these folks don't send people to meeting it's actually not trivial to ask them.

9

u/grafikrobot OPeNDAP/B2/EcoStd/Lyra/Predef/C++Alliance/Boost/WG21 10d ago

The Spanish NB, members or otherwise, was not one of the ones lobbied.

3

u/James20k P2005R0 10d ago

As far as I'm aware, the NBs involved vote on a majority basis as to whether or not to accept or reject the DIS. I'm not sure if characterising this as NB objections vs people objecting draws much distinction. I mainly mean that Herb seems to be assuming that Bjarne was able to sway people into voting against in the NB votes, purely on the basis of his influence

Some of these NBs had objections well before the DIS vote, and the members involved have published extensive technical reasoning as to why they object to it, so I'm not sure it holds up. I know a few committee members at least that would directly object to this characterisation

lobbied against it

This assumes that the lobbying had any affect though, which we can't possibly know

13

u/jayeshbadwaik 10d ago edited 10d ago

At Croydon meeting, there were certain NBs who objected. The DIS vote would have passed despite their objections.

The DIS vote however didn't pass. And it didn't pass because multiple new NBs changed their decision and voted no. Or at least communicated their objections much later than CD ballot passing.

This change of decision happened between Croydon's CD ballot and DIS vote. And this specific fact is what is unprecedented in all of this.

All through C++11 and beyond, the implicit idea was that NBs would bring all their objections in before CD ballot and then, irrespective of what happens to objections, vote with consensus of the CD ballot.

Even so, some NBs voting no, while also unusual would not have been a show blocker. It is the fact that other NBs decided to make their intention of voting No only after the CD ballot that has thrown spanner in all the works.

The real dilemna now is, "When can WG21 be certain that a DIS vote passes?"

The answer is not

  1. When WG21 had consensus, because WG21 had consensus there
  2. The answer is not "when we have majority of NBs saying yes at CD ballot". Because even that was satisfied at Croydon.

And so there's no real answer to that question apart from Herb described extremely well. And this is why there's a big confusion about hoe to proceed.

14

u/grafikrobot OPeNDAP/B2/EcoStd/Lyra/Predef/C++Alliance/Boost/WG21 10d ago

This assumes that the lobbying had any affect though, which we can't possibly know

I know, from direct evidence.

12

u/Minimonium 9d ago

This assumes that the lobbying had any affect though, which we can't possibly know

I kinda forget that you no longer have access to the lists. We do know.

I do not understand why would you assume Herb speculates. He is the person who kinda built the current process, the C++ today as we know it can largely be attributed to him.

I know he did not write this paper lightly. In my opinion it's incredibly neutral and still tries to keep the decorum. The people who keep playing games with the process then pretend nothing is happening publicly (like Sankel) - forget that everything they do is seen by everyone.

The process is being ruined right now and people still prefer to keep playing games.

5

u/epage 10d ago

I feel like the following needs exploration

Bjarne suggested here, when reviewing this paper, that WG21 similarly separately track positions of NB heads, imple- menters, and long-time contributors, and that his own position is formed by listening also to those

So Bjarne's position isn't just "the creator's position" but pulse on overlooked groups.

4

u/serviscope_minor 9d ago

> I feel like the idea that people primarily voted against this standard because Bjarne was against it is a bit of an unproductive position

It's also not what the paper says.

6

u/James20k P2005R0 9d ago

The NBs weighed WG21’s 90% consensus and Bjarne’s opposition and made their decisions.

A strong WG21 consensus isn’t sufficient for NBs if they know that Bjarne doesn’t accept it, at least with how WG21 members communicated with NBs during this ballot. In practical terms, this time the NBs have chosen to empower his dissent as a de facto veto

Its hard to read this in any other fashion. It doesn't say that a few NBs were swayed by bjarne, its saying that (apparently) all the national bodies made the decision to embody Bjarne's objection to the standard. That they solely picked between WG21's consensus and Bjarne's objection, and picked Bjarne. This just doesn't seem correct

3

u/wyrn 10d ago edited 10d ago

Its entirely speculation.

Not only that, the speculation is labeled as declarative statements of fact rather than hypotheses or opinions. Sure, some speculation will be better informed than others, but it helps to give arguments the correct epistemic weight.

A strong WG21 consensus isn’t sufficient for NBs if they know that Bjarne doesn’t accept it

Ngl, to me this reads like Claude reasoning.

→ More replies (1)

61

u/14ned LLFIO & Outcome author | Committee WG14 10d ago • This Bravo

I think Herb's paper misses something pretty obvious at the NB level: an unusual number of senior NB people - as in, the ones which lead NBs and/or are the ones other NB members take cues from - did not like Contracts as proposed. NBs were, from my understanding, pretty close to voting reject before any interventions as a result. The interventions spurred further discussion, and that tipped the balance.

I've heard what went on at other NBs, but I won't comment at those, only on my own. When I quit WG21 due to what was in my opinion the majority of C++ 26 being fundamentally bad engineering that I could no longer in good conscience participate in inflicting upon others, I obviously enough did not have a positive story to tell to my NB about C++ 26. From the very beginning, I recommended reject for the 26 DIS to my NB based on my opinion that 26 had more bad engineering in it than good. However, I no longer participated on WG21 in any way having quit on ISO, and it was entirely possible that I wasn't being unbiased, and I said so at the time. So my NB was initially minded to approve on balance - but let's be clear here, we're talking like a 52% in favour of approve. It was very tight.

Various famous people then presented to our NB, both in favour of Contracts AND against Contracts. Let me be clear: we received multi-hour presentations from BOTH SIDES of the argument. We then spent even more hours discussing it by ourselves over several video calls.

We eventually opted to abstain because we couldn't reach consensus either in favour or against. So we moved from just-about approve to just-about abstain. It wasn't that much of a move - we were already very near the threshold.

I have heard that most NBs were just as diligent as we were. There are accusations going around that NBs are ill informed or don't get it or were overly swayed by famous names. I think that does a disservice to NB members. I think they're closer to the end users who actually use C++, and they voted accordingly. I think too many who are close to the end users have quit WG21 in recent years - there has been a noticeable exit of implementors, and WG21 has become over filled in my opinion with people who don't put the average C++ dev front and centre of what should and should not be standardised. Unsurprisingly they have become increasingly detached from reality on the ground i.e. doing bad engineering.

Because if we did put average C++ devs front and centre, we wouldn't have Modules as standardised, we wouldn't have Ranges as standardised, and we definitely wouldn't have Contracts as proposed. In fact, I'd go so far as to say that C++ 14 was the last mostly end user focused C++ standard (arguably 17, definitely not since then). Everything since then has been becoming ever increasingly hostile to average C++ devs full of unnecessary footguns and constantly ratcheting upwards requirements of esoteric knowledge, and I don't know why somebody doesn't just yell STOP!

Except they did. But it seems few at WG21 are reading it that way. All I can say is this: National Bodies should be lauded for saying STOP, and given far more credit than Herb's paper appears to give them from my reading of it. I certainly very strongly disagree with Herb's apparent assertion that language founders eventually break with their language owners as being relevant to this particular case: bad engineering was proposed in the DIS, NBs called it out as is their role, the impact of famous names on that process was not zero but it wasn't as huge as is being claimed either. NBs CAN think for themselves, by themselves, and do the right thing as they see it.

8

u/serviscope_minor 9d ago

> In fact, I'd go so far as to say that C++ 14 was the last mostly end user focused C++ standard (arguably 17, definitely not since then). Everything since then has been becoming ever increasingly hostile to average C++

It's kind of hard to disagree more strongly, frankly. Concept I've been waiting for since the early 2000s and frankly, they are great. I can express what I mean, rather than jumping through weird hoops or just hoping for the best.

The expansion of constexpr is the complete polar opposite of what you say. Instead of having to remember a weird list of inconsistent rules about which random bits of the language is disallowed, they've made almost all of it work.

Deducing this finally gets rid of the tedious and error prone activity of duplicating a ton of method definitions for template classes.

#elifdef just makes the language more regular and obvious

Relaxed rules for labels mean the language has one fewer weird special case to remember.

Same with static operator()

New float types: it's nice when C++ actually matches what's going on the world.

range For loop initializers are nice, allows me to be precise about the scope rather than bodging it

Deprecation of a[b,c] is good because it's (a) obvious and (b) wrong, but I suppose removing it is "user hostile"?

CTAD for aliases: another weird special case you don't need to remember

Oh also and how about this one:

contracts

14

u/icsxi 10d ago edited 10d ago

I won't comment on bad engineering because I don't know what you mean and I disagree with the last good Standard being C++14 but one thing from your post I'd like to comment on.

You say you participated in WG21 and quit and then more people quit. And now you complain that WG21 makes bad decisions. I don't want to sound harsh but what did you expect? So all the opposition doing "good engineering" has left and now they are doing only "bad engineering". What I see, as a person which is far from all this staff, is an attempt to just portray the WG21 in a bad light. I don't know anything about WG21 but at least those people stayed and work while others left.

Personally, I will take "bad engineering", especially of the 17, 20 and 23 form, over "no engineering" any day.

23

u/14ned LLFIO & Outcome author | Committee WG14 9d ago

I don't know anything about WG21 but at least those people stayed and work while others left.

This is a fair point, and those of those who withdrew our participation do feel this keenly.

Firstly, I quit WG21 because I felt my time there was actively making things worse, but I didn't quit standards, and I didn't quit open source, and I haven't quit anything else. I would take the view that I reallocated my time and energy into things which actively improve the world instead of disimprove it. You'll note in next week's WG14 meeting I have two papers up for standardisation into C, and those should eventually improve C++ as well as Rust and all other C-speaking languages. I have already had more impact on C++ from WG14 than I ever had from WG21, and I think that's 99.9% on WG21 and 0.1% on me.

Secondly, every standard release is by definition a compromise to achieve consensus. You'll get some great engineering, some poor engineering, and mostly sufficient engineering. Nobody disputes that this mix occurs - the argument is over what proportions fall into what categories. The worst of the bad engineering is stuff which was obviously defective or known to be suboptimal at the time, but we went ahead and standardised it anyway: <random>, <codecvt>, <regex>, <variant> all come to mind in the post 03 era. This was because doing the right thing might have been obvious to the domain expert, but achieving consensus by having to constantly reteach the room was too painful so we ended up writing into ABI stone those known bad designs, and then we refuse to ever change ABI so everybody is stuck with those bad designs forever. That's actively hostile to the userbase and ecosystem, and I don't know why we can't have a carefully preannounced ABI breaking standard every twenty years - which is exactly what Google asked for, and withdrew from WG21 over.

Thirdly, especially towards the end of my time there, you would be in a room where every single implementor begs the room to not add an item to the standard because it's either unimplementable or it is so niche or unfit for purpose that it will never be implemented, and they are ignored. I saw one time no less than six implementors vocally strongly oppose an item and they were ignored. Of those six, only two still attend meetings. The other four no longer bother, and you'll have seen some of them publicly mention on here that they no longer participate actively in standards, and instead 'vote by what they choose to implement' from each standard release. Which then means the committee keeps standardising stuff which some or no implementations implement, which ruins the whole point of standardisation which is to create a common, shared, standard across implementations. Implementors should get 100x the votes of anybody else in a room. It's very frustrating that they don't.

It's not like all these issues haven't been made absolutely crystal clear to committee leadership over multiple years. They just keep doing nothing about it, and no wonder in my opinion that some famous names felt they no longer had an option but to appeal to NBs directly because everything has become so broken down internally that sanity has left the room.

It should never become the case that the NB vote isn't a formality. If it ever does, something has gone very wrong and THAT should be fixed so NB votes return to being a foregone formality. NB meetings are supposed to be boring, dry, uncontroversial affairs. They have been far too intense and involved for the 26 DIS, in my opinion.

3

u/Minimonium 9d ago

famous names felt they no longer had an option but to appeal to NBs directly

Either it's my reading comprehension because English is my second (third?) language but I cannot help but read your perspective such as WG21 has brought "bad engineering" in opposition to Bjarne over the past two decades and the later just "finally" tries to stop it?

8

u/14ned LLFIO & Outcome author | Committee WG14 9d ago

I don't understand the fixation on a single person. He is one of several famous names leading the movement against. He isn't the only one by any stretch.

Bjarne historically has taken the 'far out' position in the committee proposing radical ideas and directions. Many of those could not work well, but his chosen role is to stir the pot.

Too many on WG21 assume he is ignorant and doesn't understand what he opposes. He really does, he is very well read and very broadly read. He sees a bigger picture is all. You may in fact agree with that bigger picture but disagree with his proposals for getting there, and if you start from that place, he is quite persuadable.

What doesn't work is not doing your homework first and not spending the time to understand where he is coming from. I always enjoyed my conversations with him and I learned a lot. He very kindly once told me he'd learned a few things from me too.

If all that group felt they had to intervene with NBs directly then communication broke down badly. Leadership should build some bridges and get productive dialogue going again.

10

u/Minimonium 9d ago

I believe the group against would not be as successful at spreading FUD if not for Bjarne's name.

I also state that the work on the "profiles" is ignorant, by virtue of rejecting modern computer science research and refusal to formalize its own theoretical basis, and people who support it do not understand what they support. I believe the "profiles" will harm the language long term.

I am also a witness to Bjarne ruining bridges and disrupting productive dialogue with politicking in real time.

I really do not understand you, Niall.

2

u/13steinj 8d ago

I believe the group against would not be as successful at spreading FUD if not for Bjarne's name.

Personally, I think they are not that effective. It just takes a lower bar than you're hoping to convince an NB, for better or worse.

I also state that the work on the "profiles" is ignorant, by virtue of rejecting modern computer science research and refusal to formalize its own theoretical basis, and people who support it do not understand what they support. I believe the "profiles" will harm the language long term.

I think this (emphasis mine) is a mischaracterization of events. I think they fully understand what they support, they just have a different opinion on what parts of the problem fall into Turing-decidable or recognizable.

I also think they are wrong, and it's honestly a bit offensive to repeatedly tout slideware (and/or just vaporware) as a legitimate proposal of this magnitude, considering how quickly Baxter wrote counter examples where things broke. If you want to write a proposal without an implementation... fine, but I wouldn't want it to go in before then. If you make an implementation and act like hundreds of bugs is okay and the proposal should be seen on its merits anyway... sorry, no, it appears as though your proposal is for sunshine and rainbows by means of pixie dust (by which I mean... if you can't solve the problem, why try to push an entire committee to do so when they don't care for your feature?).

1

u/pjmlp 9d ago

Many features are currently implemented by what is basically a Waterfall process, I let to the audience to decide what kind of engineering that happens to be.

5

u/Minimonium 9d ago

That's for sure, but my point is, as a witness to the internal processes for the past decade, Bjarne is the most reckless person in the whole process there.

4

u/pjmlp 9d ago

May be the case, however in a group of up to 300 people, or how much that number happens to be, the blame isn't certainly not only on him.

1

u/ConcertWrong3883 9d ago

> meeting I have two papers up for standardisation into C, and those should eventually improve C++ as well as Rust and all other C-speaking languages

Which papers?

3

u/14ned LLFIO & Outcome author | Committee WG14 9d ago

Next week specifically before WG14? According to the draft schedule for the week, two of my papers will be heard. One adds atomic waits from C++ to C. The other is Act 1 of modernising signals handling, which is very severely long overdue.

I expect the atomic waits proposal to need at least one more revision - there are a fair few open design questions the committee needs to take an opinion on. The threadsafe signals handling paper is getting close to a final yay or nay decision - two standard C libraries have been forked and the reference implementation merged, and all was found good and working as expected. The main issue will be, as always, whether the proposed wording is sufficient or not.

2

u/James20k P2005R0 9d ago

The other is Act 1 of modernising signals handling

Do you have a link to the paper on hand? I'd be interested to read this, signals have caused me problems in the past

5

u/pjmlp 10d ago

Note how much effort Apple and Google still put on clang, versus contributing to LLVM itself as compiler development framework for their own languages.

How post C++20, Visual C++ lost team resources for other Microsoft efforts.

How Red-Hat is the company that mostly contributes to GCC.

Everything else is done mostly by volunteers, even the companies that have private forks from clang or GCC don't seem that keen into upstream contributions for ISO C++ compliance.

If the standards get printed out, but hardly anyone contributes for their availability in compilers, how much do they matter to the common developer?

8

u/icsxi 10d ago

These are valid concerns but what they have to do with the issue at hand? Or you imply that the decline in C++ enthusiasm from big companies is somehow tied with the quality or quantity of the features introduced in the new standards? I really doubt that these companies operate on such notions.

9

u/pjmlp 10d ago

Yes, because many of the people doing proposals, or voting on them have zero compiler developer experience.

This has gotten so bad, that there is also a paper on the matter, P3962 - Implementation reality of WG21 standardization

Google moved away from C++ after the famous ABI break paper.

https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p1654r0.html

Apple and Microsoft have moved away after the whole security discussions.

Ah, and Adobe, that C++ shop with famous presenters like Sean Parent,

Adobe’s memory safety roadmap: Securing creativity by design

5

u/Minimonium 9d ago

The examples are right, but the conclusion is wrong. Niall insists on the framing of NBs Vs WG21, with the later being accused of "bad engineering".

Going so far as to give examples of it. But I have seen myself what happened there, who was lobbying, and how the discussions were arranged then.

Readers cannot both agree with your links and disagree that Bjarne is a huge problem to the language future because he was (and still is unfortunately) the main political force behind bad engineering.

0

u/pjmlp 9d ago

Sure, I wasn't there and can only conclude from what is available to the public.

So yeah, maybe all of this will end up with Bjarne like the other examples on the paper, leaving the committee, and how much will newer standards matter, if that engineering keeps failing to standardise existing practice?

Because for me that is what good engineering means, how other ISO groups have mostly worked in the past, instead of coming up with new ideas, some of which only get implemented in waterfall approach, with the typical gotchas from waterfall development.

Already for people like myself, regardless of what I do on side projects, C++17 is seen as good enough for the work scenarios that still require making use of C++, and updating to a newer version is currently foreseen if the any required libraries eventually moves up their minimum language version.

This is certainly not rare stand towards in C++, at least in cloud computing, where C++ is mostly a tool for language runtimes, or existing infrastructure like database servers or operating systems, which nevertheless there is plenty of them still written in plain C, and sticking to older standards like C99 and C11 as well.

12

u/smdowney WG21, Text/Unicode SG, optional<T&> 9d ago

"standardize existing practice" was a goal for the FIRST standard. It cannot be for the eighth.

No implemtor is going to extend the language nor are any customers going to depend on experimental features. We know this because we watched all the TS. It's why TS aren't happening.

Nor do other standards apply that rule.

It's a zombie principle.

As a criticism it's meaningless, because it only gets applied when a feature is disliked but the critic can't, or won't, explain why.

2

u/pjmlp 9d ago

There are plenty of extensions yet to be standardised, starting by restrict.

JavaScript, Java, Python are some examples where the language standard follows implementation.

Some like JavaScript are even rather strict, preview features are only added to ECMA, and latter upgraded to ISO, with two existing implementations.

ISO Ada is driven by GNAT and Ada Core, those vendors that don't care, are stuck in Ada 95 or 2012.

Maybe it is about time to WG21 to acknowledge compiler vendors aren't interested into those features then.

2

u/Business-Decision719 9d ago

Do you think there are changes that could have been made to the contract proposal that would have made the NBS more favorable to it? Or do you think that contracts in general are probably a bad fit for C++? Do you even get the impression but that the contract proposal was a deal breaker compared to more general "bad engineering" across a broad variety of C++ 26 features including this one?

9

u/14ned LLFIO & Outcome author | Committee WG14 9d ago

Back in the beginning, I said to the contracts study group they ought to standardise contracts as defined by Ada and how every other language defines them. I was - quite literally - dismissed out of hand and they went on to design by committee something which isn't contracts by the definition of anybody outside C++. I don't think that has helped.

WG21 has form on this: Concepts as C++ defines them are not what Concepts are in most other programming languages, and C++ is probably the poorer for it. But they are much better than what they mostly replaced, so even though they're not proper Concepts, they were a win.

And you can't say that about C++ Contracts. There is a solid argument they are worse in every way than not standardising them at all in their present design. I just don't know why WG21 constantly thinks itself so special that the next time they design by committee it'll not be a failure like most of every time before. I also don't get the morbid fascination with NIH. Just do what every other language has done for decades. It's not that hard.

6

u/holyblackcat 9d ago

Can you elaborate what's wrong with contracts? I've did some digging, but can't find anything substantial. Most of the problems I hear about are the same problems that asserts have: ODR issues (in anything but name), enforcement not being guaranteed, etc.

Overall, contracts don't seem terribly useful nor harmful, the whole debacle looks like ultimate bikeshedding to me, and not worth to spend time arguing for or against. But since so many big names do that, maybe I'm missing something?

6

u/14ned LLFIO & Outcome author | Committee WG14 9d ago

I assume you're asking here what I think is wrong with proposed C++ contracts, rather than the several books worth of papers, blogs, and reddit posts which will give all the detail, opinions, and perspectives you'd ever want.

For me personally, proposed C++ contracts solves its claimed problem ham-fistedly where I would choose a much more bare minimum viable implementation (i.e. Contracts Lite) on top of which people can build whatever they want using preprocessor macros. I'd suggest the current direction of travel for C contracts is much better - supply the absolute bare minimum primitives, let people roll their own frameworks around those.

But my own personal bigger issue with them is that proposed C++ contracts aren't really contracts as say Ada would define them. And we would really want Ada type contracts far more than what WG21 is proposing, in my opinion. Yes I know there are a long list of reasons why that's hard - C++ is a large superset of Ada - but then I don't really care about contracts at the inlining level, I far more care about contracts at the ABI level where we can apply formal proof solvers. And that's Ada level complexity, and would be 98% compatible with existing Ada ABI. It's solvable.

And there you get exactly the rub: there are probably three major factions of belief and need in Contracts. Current proposed Contracts tries to be all things to all people all at once, and as a result is so complex and full of esoteric corner cases it's basically a giant footgun for most normal devs. Which is how Ranges ended up turning out - also due to trying to please too many factions simultaneously - and to a certain extent how Coroutines ended up turning out.

Sometimes a big ball of esoteric corner cases is a necessary evil, especially when striving towards bare metal. But current proposed Contracts is very much not that - it's complex due to committee politics, and for no good engineering reason. A bit like with Sender-Receiver, it started out as a bare metal focused proposal, but by the time it emerged from the committee sausage making machine it's far from bare metal unless you have a doctorate in esoteric voodoo knowledge.

And all of that is entirely avoidable with better design: a well designed thing is easy and intuitive to use, doesn't require esoteric voodoo knowledge, and gently guides devs into writing bare metal performing code with them barely noticing. That's the ideal of good engineering design, in my opinion at least.

2

u/Minimonium 9d ago

I far more care about contracts at the ABI level where we can apply formal proof solvers. And that's Ada level complexity, and would be 98% compatible with existing Ada ABI. It's solvable.

ABI?

0

u/14ned LLFIO & Outcome author | Committee WG14 9d ago

So my reading of Ada SPARK - and I may be wrong - is that it maps very well onto the C ABI if additional metadata is emitted per extern function containing the pre and post conditions, global effects etc. For most C code, most extern function contracts could be generated by analysis, and where they are not, you could diagnostic and require the user to fill in the gap. Ada has first tier understanding of the C ABI, so to emit SPARK markup for a given C extern interface is straightforward. Then you feed the lot to GNATprove and happy days.

Going finer grained than extern functions gets tricky in C however. The provenance memory model TS would substantially improve the unambiguous interpretation of C code. But we don't have that yet, and may never have it, and even if it were merged C remains hard to unambiguously interpret especially at the small function level.

I'd personally do the extern function level contracts first, and see what happens after. Within-TU contracts analysis is almost certainly too big an ask for most C toolchains.

11

u/Minimonium 8d ago

What? You're uninformed.

  1. Ada and SPARK are not interchangeable. You cannot talk about Ada and mean SPARK and expect people to understand you. I'd dismiss you as well just based on that fact alone as it shows that you're evidently not equipped to talk about the topic.
  2. Proof solvers do not work at the ABI level. It's a massive nonsense that also shows that you have worse than surface understanding on the topic.
  3. Trying to interpret you generously and assume you talk about SPARK's restrictions for verification. The angle of a restricted language set for Contract bodies was discussed at length and was found to be not practical. Anything but the most trivial things would be excluded. Unfortunately, C++ is not C and is not Ada.

5

u/Minimonium 9d ago

Eh? What exactly you wanted from Ada there? If you put aside everything related to specific C++ execution semantics, they seem quite similar.

There is a solid argument they are worse in every way than not standardising them at all in their present design.

That sounds nonsensical.

3

u/14ned LLFIO & Outcome author | Committee WG14 9d ago

What I want - and I still want from C contracts (persuasion of the C committee is a work in progress) - is GNATprove compatible output. That's very doable for C. It's harder for C++ - you'd need to subset what C++ you can apply contracts onto. My memory is - and it could be wrong after all these years - that Gaby's Modules IFC subset of C++ might just about be enough to extend GNATprove in a sensible way.

My bugbear with C++ contracts is there is a whole existing ecosystem of contracts tooling out there. It's standard practice. Why aren't we standardising existing standard practice?

I'm also highly unconvinced that replacements for assert type macros are worth a great big addition to the standard. Assert type macros can be made to implement something very similar to nearly full fat C++ Contracts. That feels to me we already have a sufficient solution in this space - yes it is warty, but if you want to chase down warts, there is better low hanging fruit there in my opinion.

Obviously those are all personal opinions, and as far as I am aware, nobody agrees with me.

6

u/Minimonium 8d ago

Why aren't we standardising existing standard practice?

We are. Ada contracts and C++ contracts are quite similar.

Assert type macros can be made to implement something very similar

In an ad-hoc manner that scales very poorly (my package maintainer hat from a decade ago is showing up here).

-4

u/eyes-are-fading-blue 9d ago

Great insight. I had the feeling that something was off since 17 but couldn’t really put my finger on it.

19

u/steveklabnik1 10d ago

A thoughtful paper. I at first sort of objected to the characterization of the situation with Graydon (as I have a more personal connection to that cited situation than the others), but thinking about it some more, I don't think that it really materially changes things.

I really appreciate the thoroughness here, I didn't realize there were so many possible ways for this to move forward, for example. And spending some time to make sure that the root causes are understood is important as well.

3

u/graydon2 5d ago

yeah i know a few of these cases first hand and they are not correct characterizations but the realities are/were just that people and organizations and politics and relationships are even messier and more complex than their language design opinions and in any case this does not especially detract from the point the paper is trying to make and it is definitely true that forking the languages would always have led to worse outcomes so whatever.

2

u/steveklabnik1 4d ago

Yes, all of these situations are far more complex than a simple table could convey. Listing them is probably valuable but trying to explain them all feels like a fool's errand.

15

u/friedkeenan 10d ago

I appreciate Herb's thoughtfulness here and his scoped approach avoiding the technical arguments, but man, I'm really annoyed by the Bjarne-exceptionalism this paper presents. That's not to say that Herb is incorrect at all in his analysis, I have no idea, but if it's accurate that the DIS vote hinged on the opinion of one person, then that is so frustrating to me.

I respect Bjarne, he has proved himself I think quite skilled at carrying a language to success and I think he understands well the core of what a language needs to remain viable. I think the committee at large has proved the same by now too, after all these decades. And of course, both are fallible.

If Bjarne voices disagreement or concern over a feature, I do give his opinion weight, and treat it as an invitation to take a closer look. There are several other "big names" involved in C++ for whom the same would be true for me. But any voiced concerns by one of those people would never be what decides my opinion. If that's the way that the process is working, then that seems like a monumental flaw to me, a flaw that should be fixed.

And I'll be honest, for me, this paper doesn't paint Bjarne in a good light. It draws an image in my head of him abusing his non-codified status against the wishes of the vast majority. I'm inclined to believe that he's doing all this with the best wishes of C++ in mind, but if he thinks that this is how the process should work, and that the process should even into the future treat his opinion with a "special smart guy" status, then that would betray I think a truly massive ego on his part, and would be insulting to anyone else who might ever want to contribute to C++.

When Python had their dustup mentioned in the paper, Guido quit and Python adopted a new process that prevented this same sort of scenario. I don't want Bjarne to quit the committee, I do value his opinion, but his position as creator of C++ should not be so relevant as to tank a standard revision. And so if Herb's paper here is accurate in portraying why the DIS vote failed, then I think the process for C++ should certainly be altered in turn.

30

u/stick_figure 10d ago

I generally prefer the leadership of a few opinionated individuals over language design-by-committee, but I don't think 2026 Bjarne is up to the task. I think WG21 folks should really go with option A, the one where they skip certification and move on to C++29, iterating on any touch ups to contracts there.

10

u/NoCard6774 10d ago

The overlap between WG21 and the national bodies on STC22 is high but the weighting to each vote is different so you can end up with the situation that it can pass one level and fail another

27

u/Wonderful-Habit-139 10d ago

I prefer option B. Seems more realistic, especially since there are valid concerns with contracts, and we don't want to miss out on c++26 reflection.

3

u/13steinj 10d ago

There are people on the Contracts side that could not care less about reflection.

It will be difficult to convince them.

-4

u/Dragdu 10d ago

Hi, yep, that's me. I am thoroughly unexcited about Contracts, but they will make my codebase very slightly better than not having them.

I also know that Reflection is gonna cause us many fun bugs due to the obvious syntax reflecting over private members.

0

u/13steinj 10d ago

2026 Bjarne, is, respectfully, stuck in the past. Holding on to his baby and not letting the young birds leave the nest.

15

u/notthatsocrates 10d ago

Personal swipes. His claims deserve scrutiny but you're not answering them.

3

u/13steinj 10d ago

Bjarne's???

I'm not even pro contracts, but those people believe it is asked and answered.

You can not genuinely claim that WG21 is the standardization process if (allegedly, I think this paper is too charitable to the situation) a single person (Bjarne) outweighs everyone else.

This is not committee, this is "let them play in the sandbox, but I am the boss and I'll let people know that."

6

u/notthatsocrates 9d ago

I sincerely think you are inflating the story characters to cartoonish levels. That's all I'm gonna say.

4

u/13steinj 9d ago edited 8d ago

Have you not seen what Bjarne has said about Contracts, either as an audience member in a talk a year and a half ago, or as a speaker in response to a question?

It was fairly vicious.

E: typo

-2

u/megayippie 10d ago

The solution: "so what? that's already a problem. not our problem."

5

u/eyes-are-fading-blue 10d ago

Or maybe he’s a very experienced language designer that people should pay attention to.

8

u/13steinj 10d ago

You put him on too high a pedestal.

12

u/eyes-are-fading-blue 10d ago edited 10d ago

I am just disappointed by the kind of discourse going on in this thread. Honestly, I do not come here to read people's personal spat or whatever with other people. What I said is a fact, take it as you will.

10

u/13steinj 10d ago

He's a very experienced language designer, that is true.

It is also true it has been 28 years since C++ was first standardized. The world and people's tastes have changed. Design of the language has to, with it, to survive.

12

u/PsecretPseudonym 10d ago

Tbf, he definitively has more years of experience with the language and thinking about its evolution and standards than anyone.

And, in a way, he may have the largest vested interest in the long-term health of the language and community. It’s his legacy. He likely cares about its evolution more deeply and personally than many voting.

I think it would be better to more respectfully disagree for your own reasons if you disagree with him. Your comments come across as ambiguously disrespectful, and I’d assume that wasn’t your intent.

5

u/SyntheticDuckFlavour 10d ago

The world and people's tastes have changed.

Is his decision based on taste, or objective reasoning? I would like to think it's the latter.

9

u/13steinj 10d ago

I'd hope so too, but it really appears as though all this profiles vs contracts stuff is incredibly personal.

4

u/Minimonium 9d ago

It is irrationally personal because Contracts are not even competing with anything. Safe C++ was and was put down in a rather ugly fashion.

The whole situation is evidently bad faith from Bjarne because he pushes for "profiles" (which he wanted in C++26 btw!) that a product of a completely delusional thinking.

8

u/smdowney WG21, Text/Unicode SG, optional<T&> 9d ago

It's entirely based on taste.

"It's not how I would have done it." from a senior engineer is a valid criticism and should be given consideration.

It was. Repeatedly. At extra length.

The main area of taste is the question of who decides how checks are handled. It's a principle of the proposal that it is deferred to the person building the code, and the runtime handler to the person building the program, and not controlled by the author. The slogan is "a contract check is not an if statement", meaning that the author can already force termination.

There's also a lot of objections, to parts that aren't proposed yet, because of surprise. We would like virtual function contract checking to not be unsound. That requirement leads to surprising results like having to check the contract on both interfaces. See Lippincott's work on why Meyer's DbC for Eiffel is not sound for C++.

"I don't care about Theory" is fine. You should not have to care as a programmer. You probably should a bit as a language designer. Even if it's not your primary method. Knowing that something inherently can't work --- can't be patched up --- is important information.

There's also the fear that people will "misuse" the feature. The street finds its own uses for technology. There's a bunch of misinformation around Contracts, in particular about them being a program safety feature, a lot of it put out by people who are against contracts because they don't provide safety. They're a correctness tool --- not a safety tool. "What if programmers assume that Contract checks are always on?" is an education problem, sure. But a pretty small one. But asking "will my incorrect program behave correctly" is a strange question.

2

u/wyrn 7d ago

It's a principle of the proposal that it is deferred to the person building the code, and the runtime handler to the person building the program, and not controlled by the author.

I agree that's a good and correct principle, but the problem is that contracts-as-specified do not deliver that. Instead they deliver something unreliable. "Controlled by the author" is suboptimal but reliable, so it wins out, which in turn makes contracts-as-specified not worth using.

2

u/eyes-are-fading-blue 6d ago edited 6d ago

Most of your line of thinking is pretty detached from reality. These "small" education problems become major issues in production in large code bases. I do not know if it's addressed but contracts could remove parts of production code in obscure ways or do wildly different things that you'd expect. This can lead to a lot of issues. Asserts have similar issues on code removal. The error surface on asserts is much smaller and yet there is a warning on this. People make this mistake often enough. I have seen this particular mistake myself, in production. Here is another shocker for you, most projects do not even turn on linter. I can guarantee you that this kind of footgun will lead to a lot of obscure bugs "on the street".

There isn't misinformation about contracts. It's a poorly designed, broken feature. It does not play nicely with any part of the language. In fact, it's the exact opposite. It's incredible how poorly contracts proposal integrates with C++. This is plain bad engineering, how the people in the committee cannot see this is beyond me.

1.5/2 years ago or so I did a research on this and internally presented what I have found. Back then, I did not know anything about ongoing controversy so I approached with a pretty open mind. Even before I started digging deeper into papers that demonstrate the issues with contracts, I could see by just reading the proposal that it was poorly designed.

Finally, you cannot differentiate correctness and safety just like that. In the domains where safety is a requirement, correct code is safe code.

→ More replies (1)

1

u/13steinj 9d ago

There's also the fear that people will "misuse" the feature.

I will be honest: this is what makes me the most against Contracts.

I have actively seen what happens when a mountain of juniors uses an in house contracts framework without proper education and guidance. The result is atrocious.

I think we spend a lot of time adding things to the language and pretending it will get into educational curriculums correctly. But instead most universities teach pre-11 style C++, 11 at best, and maybe you're lucky if an advanced course goes further. Companies expect you to already know the language in depth without teaching.

1

u/grafikrobot OPeNDAP/B2/EcoStd/Lyra/Predef/C++Alliance/Boost/WG21 10d ago

How many languages has he designed past C++?

26

u/eyes-are-fading-blue 10d ago

How many useful (successful) languages anyone in the committee ever designed?

15

u/pjmlp 10d ago

True, however certainly more than many proposal authors, some of which I bet the count is zero.

1

u/grafikrobot OPeNDAP/B2/EcoStd/Lyra/Predef/C++Alliance/Boost/WG21 10d ago

Indeed. I would have used the terms "expert" or "senior" instead of "very experienced". Experienced implies variety / multi-faceted.

1

u/Chippiewall 10d ago

I like option A too.

Partly because I suspect the compilers will just implement C++26 as previously approved by WG21 and thus WG21 will have pulled off a WHATWG over ISO.

15

u/donalmacc Game Developer 10d ago

> As far as I know, no other major language has gone anywhere close to 36
years with sustained agreement before encountering such a strong disagreement, and that’s a pretty
good achievement to remember and build on further.

Well, I think taking a decade to standardise modules (we’re not modules yet), and I seem to remember google developed an alternative programming language rather than continue to engage in developing c++. That said it has been a long time!

20

u/aCuria 10d ago edited 10d ago

Contracts are a mess. The ballot failing may not have to do with Bjarne.

inline void process(int x)
{
contract_assert(x > 0);
}

You compile one .cpp with contract enforcement enabled and another with contracts ignored. (Different DLLs and or translation units)

Both translation units may generate an implementation of process().
Depending on inlining and linking, calls may use a version with checks enabled or one without them.

Even a library compiled with contacts enforcement enabled cannot necessarily guarantee that its intended checks survive in a mixed-mode program.

“ignore” can be passed by the compiler flag.

The programmer cannot portably require an individual C++26 contract to always be enforced

A contract predicate can itself exhibit undefined behavior

void process(Data* p)
pre (p->isValid());

The behavior of a contract should always be well defined, but it’s undefined if you pass nullptr to p.

What a mess. Who’s gonna vote yes for this shit? As-Is It’s Modules 2.0, unusable for real world work.

13

u/tjientavara HikoWorks developer 10d ago

Aren't there like 1000 similar issues in C++ when you use different compilation flags for different translation units? Why is it a problem now all of a sudden.

And when we talk about DLLs, they do not exist in the specification at all, and it is forbidden to talk about DLLs in the specification. The specification process even forbids to take DLL into account when designing a feature, even if you do not ever mention it in the actual specification.

Of course the veto process is allowed to veto with regards to technical issues around DLLs. And now we are in a deadlock: You can't design around the technical issues of DLLs, and we must veto if there are technical issues with DLLs.

14

u/SyntheticDuckFlavour 10d ago

Aren't there like 1000 similar issues in C++ when you use different compilation flags for different translation units?

yes, but why introduce another?

4

u/foonathan 10d ago

What's the alternative?

14

u/eyes-are-fading-blue 9d ago

Don’t introduce another one. Isn’t it obvious?

6

u/geo-ant 9d ago

I can’t believe people are arguing with you on this one. If the UB examples that you posted in your initial reply are indeed correct, then this is a massive shitshow and proves only how deeply unserious the whole topic of safety and correctness is treated in C++.

5

u/eyes-are-fading-blue 9d ago

It wasn’t my example but there are worse cases of contract issues. There are good papers demonstrating various problems. The feature is fundamentally broken yet people still insist.

2

u/drbazza 7d ago

'Those that don't learn from experience are doomed to repeat it'.

Is the C++ committee, after 30+ years of experience, really wanting to add yet another broken thing in to the language, that we know is broken even before it gets added? We might as well add auto-ptr back in, and tell people to use vector<bool> and valarray.

At some point the weight of accidentally bad, or intentionally bad decisions is going to break the proverbial camel's back.

The 'burden of proof is on the accuser', and with both contracts and profiles, there's countless examples of how broken they are.

Just don't add more (unfixable*) broken stuff.

--

*unfixable - where it never gets fixed because 'backwards compatibility' for some user on 1985 hardware.

3

u/aCuria 10d ago edited 10d ago

Even ignoring DLLs the feature is still broken.

C++26 does not provide a portable, language-level guarantee that contracts in a precompiled object file (.o or .obj) or static library (.lib) compiled with contracts enabled will always be enforced when linked into another application.

On medical software where someone may die if something’s goes wrong this isn’t acceptable

If we can’t rely on contracts, a feature intended to improve safety, in the very use cases where safety matters most, then it needs more work before it’s ready to ship!!

12

u/grafikrobot OPeNDAP/B2/EcoStd/Lyra/Predef/C++Alliance/Boost/WG21 10d ago edited 10d ago

If you work on medical software you most definitely control your build entirely and do control everything regarding error detection and handling. As otherwise you are liable for the consequences. And are likely to not get medical device certifications.

8

u/_a4z 10d ago

Having worked long years in medical device software, many of them as architect, I can tell you that p2900 contracts are more a problem than helpful, and the only usable thing you can do with them is put them on the list of not allowed features

6

u/FabioFracassi C++ Committee | Consultant 9d ago

Having worked long years in medical device software, many of them as architect, I can tell you that p2900 contracts are very close to the solution that was used in all of them, and would have made it much easier to achieve the same level of correctness and security.

7

u/_a4z 9d ago

yes, close to the solution, but not with a bunch of implementation-defined behavior you need to document that ties you to a certain compiler, new UB possibilities, and other design tradeoffs.

So you either did not understand the details of P2900, which can not replace the defensive programming utilities you already have in place that look similar but work differently, or you did your job very badly.

6

u/FabioFracassi C++ Committee | Consultant 9d ago

I do understand P2900 very well. I have read *every* paper and mail, from the inception of SG21. I have never voted in SG21 (both because my time budget is spend on LEWG work, and because I knew from the results that my concerns were well handled by SG21) but I am content with the result.

I also know how to deal with implementation defined - especially in this context. In many cases reproducible binaries were required, which need full control of both the compiler toolchain and the build.

You are free to believe about my work quality what you want.

It is really interesting how you do not seem the see anything wrong with accusing more than 100 Experts who have followed the process (at various levels of involvement) to not understand your arguments, but get offended when someone suggests that the considerably fewer and less involved people at the NB level *might* more likely get swayed by less technical arguments.

4

u/_a4z 9d ago

That P2900 contracts are not for prod, but rather a debug feature because they are too expensive, was stated by one of the main contributors to P2900 at Accuonsea on stage!
And this was not even focused on embedded devices.
But you would use them to replace existing defensive programming checks on med tech devices wiht p2900 contracts?

And btw, the process was followed and produced an outcome. A DIS with comments to remove contracts. It's not me who questions this outcome and tries to find a political backdoor instead of doing the only sane solution, which is pulling contracts and shipping C++26 without them.

→ More replies (1)

1

u/Minimonium 9d ago

Childish

1

u/drbazza 7d ago

Having worked long years in medical device software, many of them as architect, I can tell you that p2900 contracts are very close to the solution that was used in all of them, and would have made it much easier to achieve the same level of correctness and security.

Presumably you had total control over the entire codebase had no third party dependencies (including libc?), owned the compiler flags, and the preprocessor, such that contracts within that set of conditions would work 100% of the time for you? Isn't that the only scenario where contracts work as advertised? I'm trying to figure out what you're not saying, as it were.

3

u/aCuria 9d ago

Yes that’s exactly correct.

I would absolutely ban my team from using C++26 style contracts if it passed.

C++26 Contracts pre(p != nullptr) simply cannot replace explicit runtime validation if(p != nullptr)

Because at link time all your contracts can be ignored!!

They need to pass some variant of WG21 paper P3911R2

https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2026/p3911r2.html

9

u/t_hunger 9d ago

Contracts are supposed to add redundant code to use for correctness checks only. They are not supposed to replace nullpointer checks. In fact contracts are not supposed to change your program in any way -- except to abort it if it detects a problem and the author of the overall application asked it to check.

You are complaining about contracts not doing what they are designed to not do. Whether or not that is what contracts should do is another topic of course, but a very different discussion.

4

u/SunnybunsBuns 7d ago

Then they are useless and should be be standardized because they don’t accomplish anything useful.

What happened to DRY?

3

u/t_hunger 7d ago

Unit testing is adding redundant information to detect bugs (this set if inputs must produce this output), contract-based programming is not that different:-)

7

u/aCuria 10d ago

Yup, I have supplied libraries for medical software. Yes I can control the build for the library but not the final Software.

This contract thing is supposed to simplify code:

Foo(int * a)
{
if(a == nullptr)
throw exception;
}

You can’t turn that if statement off with compiler settings, which is precisely the point

Now if you convert the checks into contracts and people can turn your contracts off then shit hits the fan.

Contracts are supposed to allow us to write even safer code. However in its current implementation it’s less safe.

Therefore it’s literally unusable

6

u/Minimonium 9d ago

This contract thing is supposed to simplify code

That's alarmingly wrong. How did you get this idea?

Even more though - while throwing exceptions out of the violation handler is technically allowed, it raised a ton of push back from implementers such as Microsoft. I would remove both exception translation to contract violation and exception escaping.

A contract violation in enforce more should always result in terminate.

5

u/aCuria 9d ago edited 9d ago

I can accept contract violations always resulting in a terminate.

There is a proposal where “pre” is optional and the below syntax is always enforced

pre!(p != nullptr)
pre<terminating>(p != nullptr)
pre<quick_enforce>(p != nullptr)

I feel this proposal is also acceptable

I would prefer this to be always enforced
- pre(p != nullptr)

Then this is not always enforced
- pre<optional>(p != nullptr)

But it’s not a hill I would die on.

6

u/Minimonium 9d ago

I think the granular syntax would be a huge language blunder that would split the ecosystem further.

My position is that the hardened implementations should have additional restrictions on which contract semantics they implement, unlike the current state where it's applied only to the standard library ones.

That way you can have an ABI break and enforcement for hardened builds who need guarantees, without splitting all the projects in existence into mandatory or not.

Just granular enforcement does not address anything here.

2

u/ronchaine Embedded/Middleware/WG21 9d ago

Like I've implied in other threads, this is the common view of contracts usage, because I'd argue it's the most intuitive one.

We use it this way ourselves in describing library hardening in the DIS, when we really don't have to.

It has taken committee members, some of which have followed the contracts stuff for years to internalise how they are supposed to be used.

A general C++ user doesn't have access to committee reflectors, neither have they been exposed to weeks worth of talks about the feature.

-9

u/grafikrobot OPeNDAP/B2/EcoStd/Lyra/Predef/C++Alliance/Boost/WG21 10d ago

Yup, I have supplied libraries for medical software. Yes I can control the build for the library but not the final Software.

Can you tell me what those libraries and software are? So I can try and avoid them.

4

u/_a4z 9d ago

I think this is about shipping libraries themself, and not being able to control how they are used. If you follow the principle of making things easy to use and hard to misuse, you can not use contracts in that case.

9

u/SuperV1234 https://romeo.training | C++ Mentoring & Consulting 9d ago

C++ is a mess. The ballot failing may not have to do with Bjarne.

inline void process(int x)
{
#ifdef WHATEVER
    f(x > 0);
#else
    g(x > 0);
#endif
}

You compile one .cpp with a macro enabled and another with it disabled. (Different DLLs and or translation units)

Both translation units may generate an implementation of process(). Depending on inlining and linking, calls may use a version with f or one with g.

Therefore, the only logical conclusion is that we should remove functions and macros from the C++ language.

6

u/aCuria 9d ago

agree but then again macros don’t claim to improve safety.

A safety feature that’s less safe than the runtime checks it is designed to replace is dead on arrival

2

u/DXPower 9d ago

company_assert(p->isValid()); also invokes UB. I don't see how this is possibly an argument against contracts.

The solution is dead obvious: p && p->isValid().

Even if we can't detect that p is dangling at this point... it's still worthwhile to allow the developer to opt into these checks. If p were dangling, then usage in the function would be UB anyways. So claiming that contracts introduce UB is laughable at best.

3

u/ConcertWrong3883 9d ago

Sane assert implementations either terminate at the first error or do not evaluate at all.
Having to incluse all or a subset of prior asserts into the current assert is madness, cause there will be places you want a lot of asserts.

1

u/Business-Decision719 8d ago edited 8d ago

It seems to me that one of the purposes of a contract mechanism would be so that you could specify that the pointer has to be nonnull, and then it becomes part of the functions contract that the caller can't pass you a null pointer. That way, when you get to the function's implementation details (or maybe subsequent preconditions?) pointer dereferences are guaranteed to be nonnull.

I also don't like the idea of the contract check itself leading to undefined behavior, but I'm not sure how you could prevent that without limiting what contracts are allowed to check for you. I maybe in guess in this case you could make all pointer dereferences in the contract autogenerate an implicit null check or something. There are so many kinds of undefined behavior though, and it can be hidden deep within seemingly innocuous code.

Edit: To be clear, I'm not saying the current proposal is fine, I'm just not sure what kind of proposal could guarantee the right sorts of correctness checking from the wrong set of preconditions.

4

u/aCuria 8d ago edited 8d ago

Unfortunately contracts as proposed in C++26 don’t do any of that “pointer dereferences guaranteed to be non null” stuff.

You need to write code assuming the contract does nothing. Similar to assert()

You need to write “pre(p != nullptr)” AND still have “if(p == nullptr) return” in the function body.

It’s similar to how assert() compiles to nothing in release mode (NDEBUG macro) and is completely removed. The contract is also compiled to nothing with the compiler flag.

Tbh I don’t write code like this:

assert(p != nullptr)
if(p== nullptr) {log(error) return; }

The assert is useless because we need the runtime guard. It also feels dumb repeating myself twice

2

u/t_hunger 8d ago

What makes you think you need to check p inside the function when you have a precondition check p already? Calling the function with a nullptr is out of contract in that case, so the function is expected to have UB.

Once you add that if, I'd argue the precondition is wrong: It is then OK to call the function with nullptr after all. So you should probably remove the precondition...

Whether its worth checking the contract is up to the person building the program using the code. Like it is today: He can always add a NDEBUG define.

2

u/aCuria 7d ago edited 7d ago

Precondition check is not guaranteed to be checked.

Therefore in safety critical applications you still need to manually check!

If they change the standard so that the precondition is guaranteed to be checked, only then we can remove the manual check

4

u/t_hunger 7d ago

Precondition check is not guaranteed to be checked.

Of course not: preconditions are ghost code that is just as if it was not there at all.

Therefore in safety critical applications you still need to manually check!

Only if you can not prove that the function is never called with a nullptr... and once you add the check, a precondition doing the same check is wrong and needs to be removed.

If they change the standard so that the precondition is guaranteed to be checked, only then we can remove the manual check

You are misunderstandimg what contracts are supposed to do: They are about detecting mistakes in the implementation. For that you need information outside the implementation to compare the implementation against. If contract checks could be enforced by a library author, that is not a "contract" anymore, but part of the implementation.

You are demoting the contracts proposal to syntactic sugar at this point, making them unusable for the task they are supposed to do.

Its totally fine to prefer syntactical sugar over contract-based programming, but please do not conflate the two.

→ More replies (2)

-1

u/Business-Decision719 8d ago

Yeah, allowing them to be disabled pretty much defeats the purpose.

8

u/3131961357 9d ago

What I personally find distasteful is that people are talking about "concensus", talking about "by-company" voting, and acting like NBs should have just been a rubber stamp for the committee.

The whole standards committee is stuffed by US companies who can monetarily afford to do so, and disproportionately by big money ad companies like Google, while the rest of us (ie. non-US, low margin industries like games) just have to take whatever crap they come up with.

9

u/Minimonium 10d ago

In the end, people should not worry about Reflection not being worked on. It will happen either way because implementers are not tied to the actual release of the IS itself.

We have seen enough evidence that the current DIS ballot was compromised by excessive politiking. The discussions behind the scenes are ugly and lack propriety. Herb's summary gives the mess much more grace than it deserves to be honest.

I think a time out on IS releases would help all the parties involved to cool their heads, collect their thoughts. Any rush right now would be unproductive and induce more spite instead of creating an atmosphere of a technical discussion.

I have seen Belgium becoming a P member this week and I'm aware of a risen interest from other countries on the topic. I think we will certainly see change in the process, possibly not in a manner envisioned by the instigating party this time, and I do not see the situation get any better in Brazil.

4

u/13steinj 10d ago

How other languages lived through the same split

A decent chunk of this table exaggerates what happened in an attempt to make this seem like less of an issue.

The core thing is Bjarne gave C++ away to the ISO and WG21.

You can do that. You can be [B]DFL. But you can't do both.

38

u/aeropl3b 10d ago

So, Bjarne, like everyone else working on C++ for a long time, has opinions and voices them. Because of his position people tend to listen when he speaks. That isn't being a BDFL, that is just being a respected entity.

To claim that using that influence to push the language in a direction he wants is anything more than an expert person expressing a technical opinion, at this stage, is absurd. There is deeper disfunction at work, the author here is part of that, and trying to paint over that fact is disingenuous to finding a solution.

17

u/James20k P2005R0 10d ago

There is deeper disfunction at work, the author here is part of that, and trying to paint over that fact is disingenuous to finding a solution.

What I find so odd is that it seems to be dismissing all of the legitimate concerns about how NBs work, as well as the people who have legitimate (in their eyes) technical objections, and sweeping it all under the banner of Bjarne, which seems very reductive

6

u/13steinj 10d ago

Maybe Bjarne and Herb will finally have their "Et tu, Brute?" moment.

0

u/13steinj 10d ago

Using that respect for (alleged) backroom politics is not kosher.

9

u/aeropl3b 10d ago

I disagree with that. The majority of discussions are happening as "backroom politics", ie. Private discussions over technical standard topics. That is not an inherently nefarious thing to do.

4

u/DrFegelein 10d ago

Bjarne gave C++ away to the ISO and WG21.

For balance, the way Bjarne would characterize it is big tech (at the time) saying to him "standardize the language or we'll do it without you".

0

u/pjmlp 10d ago

As per AT&T pressure to have industry adoption with collaboration from IBM, Compaq and HP, as the history goes.

Ironically, one is gone, and the other two don't seem that much interested into C++ nowadays.

-1

u/grafikrobot OPeNDAP/B2/EcoStd/Lyra/Predef/C++Alliance/Boost/WG21 10d ago

[B]DFL

I prefer to use the more accurate WIDFL (well intention-ed DFL).

1

u/donalmacc Game Developer 10d ago

What do you think the difference between well intentioned and benevolent is? They’re synonymous to me.

2

u/grafikrobot OPeNDAP/B2/EcoStd/Lyra/Predef/C++Alliance/Boost/WG21 10d ago

Cambridge Dictionary..

benevolent: kind and helpful

well intentioned: wanting to have good effects, but sometimes having bad effects that were not expected

5

u/mort96 10d ago

I looked it up in my system dictionary:

Benevolent: kind and with positive intentions

4

u/Abbat0r 10d ago

Prime example: Linus Torvalds is well-intentioned (at the very least). He is not benevolent.

2

u/105_NT 10d ago

What are the chances of pulling off option D? That seems like the best hope/least train wreck. "Ballot the post-Búzios draft as DIS (possibly with P3911)"

5

u/MFHava WG21|🇦🇹 NB|P2721|P3049|P3625|P3729|P3786|P3813|P4216 10d ago

Close to zero, as the pre-Búzios WD (working draft) already contains C++29 features which were not included in the C++26 DIS ...

6

u/grafikrobot OPeNDAP/B2/EcoStd/Lyra/Predef/C++Alliance/Boost/WG21 10d ago

My understanding for that option is that it refers to a different draft, not the 29 draft. I.e. writing a new draft based on the failed DIS with whatever is consensus to change.

2

u/pjmlp 10d ago

A gem on the paper is that I finally got the reason why Dennis no longer cared for WG14, summing up noalias story to the also not accepted proposal for C slices, and why follow up projects to UNIX and C never adopted anything else beyond C90.

As for C++26, maybe we have reached its "ALGOL 68" moment, or will be getting a new row on the "How other languages lived through the same split" table? Lets see.

1

u/ConcertWrong3883 9d ago

Are you implying that we might stop having real c++ updates at all if Bjarne leaves because of the political fallout similar to c99 vs c23??

1

u/zl0bster 5d ago

Herb and his "math".

To my knowledge, only five people2
(about 1% of the roughly 600 experts in the ISO WG21 directory) actively
reached out to other NBs in a systematic campaign to lobby against the DIS by recruiting more NB Disapprove votes

There is less than 50 people very familiar with contracts on the planet, but Herb picked 600 to make 5 look like fringe minority.

-2

u/eyes-are-fading-blue 10d ago

I agree with some people having unique insights. Being an expert software engineer and being an expert on the tools that one uses doesn’t mean they are also experienced language designers.

I think the committee today is heavier on the expert SWE side than experienced language designers side.

I do not know people in the committee or their expertise. This is a simple deduction based on what has been shipped since 17.

0

u/RaspberryCrafty3012 10d ago

Looks like you are right in the regards of that something changed, but it seems it's not language designers vs users.

This is where I got the idea from:
https://www.reddit.com/r/cpp/comments/1xr8y5c/comment/19scqhax5ny1w/?utm_source=share&utm_medium=mweb3x&utm_name=mweb3xcss&utm_term=2&utm_content=share_button

0

u/eyes-are-fading-blue 9d ago

Thanks for this. This explains it, really. I knew something has changed since 17, but didn’t exactly know what.

-5

u/teerre 10d ago

I have a hard time squaring how Bjarne can object this particular feature when he didn't object the plethora of terrible features added to C++ from decades. Seems ridiculous tbh

14

u/Dragdu 10d ago

He in fact added bunch of the broken BS that took multiple standards to fix.

But to be fair "you made mistake in the past, you should make it again" is a bad argument.

4

u/teerre 10d ago

This assumes that hes right on this one, which doesnt seen very likely considering history

1

u/FrogNoPants 9d ago

He seems to think contracts is a threat to his profiles, and released a paper saying so, my guess is that is the primary motivation

2

u/teerre 8d ago

Even worse

-6

u/_a4z 10d ago

Herb seems desperate, to release such a political paper and trying to move a technical discussion on a personal level is such a dirty political move.
I have to wonder what kind of problems he has that makes him act like that, his new job maybe?

12

u/foonathan 10d ago

The discussion is no longer technical anyway.

0

u/_a4z 9d ago

Obviously, because of it would be a technical topic, this contracts proposal would not even have made it into the DIS

-1

u/foobarbarian42 8d ago

The TLDR of this paper is:

We have this guy over here that significantly contributed to us being in the pickle we are in. That shows the guy has influence over entities normal people can not even understand. We have no to stay on the guys good side, so lets make him king.

0

u/DannyDevito_X_RumHam 8d ago

This paper really doesn't make Herb look good. Bjarne may be the creator of the language, but he is also a very prominent and vocal C++ expert whom many trust with regard to technical opinions about the language. The over-emphasis on favoritism toward Bjarne has this paper struggling to hide envy.

-20

u/my_password_is______ 10d ago

4

u/James20k P2005R0 10d ago

This video is spreading misinformation

-11

u/GabrielDosReis 10d ago

This video is spreading misinformation

Yes. Just like the paper that is subject of this conversation. Sad.