Post

sounds like some good stuff is happening with #cpp 26. congrats to @thephd.dev for getting embed in. im personally skeptical of contracts (that includes #rustlang btw) but that's been going on even maybe longer than embed was. them landing is a huge deal

the Profiles votes are shocking. I was under the impression that this was the last meeting for cpp26, but i also could be wrong about that. but all of the votes in previous times were very heavily in favor, and now, they're clearly split evenly or a bit against.

okay so there is another meeting but due to a bunch of procedural stuff that i don't care to type out, this does mean profiles are dead for C++26, in my understanding. they are going to produce a "language safety whitepaper" though

We have a collaborative r/cpp report landing soon which will explain the whitepaper. I think it’s a good thing, removes time pressure and gives more freedom to advance rapidly and land something sooner.

It's going to take a bit more time for the collaborative trip report to make r/cpp, so here's an explanation on what happened with C++ profiles, their relevance to safety/security, and why this is a great outcome for quality of the feature and speed of delivery.

Specifically, I had no idea that “white paper” is a term of art with some weight here! I am used to it just being “a blog post but as a PDF”. Very interesting!

0 reposts5 likes

Yeah! I think ISO has had this forever, but in ~September they emailed the convenors and said "hey we have this thing that SC22 can approve without us (ISO) being involved, wanna use it more?". We need to be careful about how we use it tho. Can't be low quality, nor too fast, nor always breaking.

Getting broad and reviewed agreement before we lock something in for production code in the compiler seems like a useful thing. There are a lot of sharp and dangerous corners in this space, and as much as I want it, landing for 26 was frightening. This gives us a way to not hold everything up.