Post

I was looking into this out of curiosity, and I'm not sure I'm understanding this right - C++ holds binding votes on whether to include sets of features, *before* those features have an implementation? There's no "test out this experimental feature" phase? That can't be a good idea

I mean "C++26" should probably be "hey Fable, rewrite this in rust" (context: C++ was my first language and I spent an aggregate decade writing it in anger, mostly C++98 and C++11)

Yes, contracts finally made it in after like a decade of back and forth. And then Bjarne regretted it and was threatening this veto. We haven’t gotten an official reason yet but this situation is my guess

I don't follow. Are you saying that Bjarne personally said he disliked contracts and the national bodies voted against the standard because he said that?

I don’t suppose you can give me or link me to an ELI5 that provides enough context that I can talk about this at the ISO-IEC/JTC 1 plenary in Dublin starting 09 November?

If this is helpful, this is an extremely high-level overview of my understanding: bsky.app/profile/jxf....

Here's a brief explainer thread for what just happened around C++ 26. C++ contains two new features designed (in part) to improve safety. There's been increasing pressure from governments and cybersecurity organizations for the adoption of languages that are memory safe by default.