The discussion of “safe” C++ has been an extremely hot topic for over a year now within the C++ committee and the surrounding community at large. This was mostly brought about as a result of article, after article, after article coming out from various consumer advocacy groups, corporations, and governments showing time and again that C++ and its lack of memory safety is causing an absolute fuckload of problems for people.

And unfortunately, this means that WG21, the C++ committee, has to take action because people are demanding it. Thus it falls onto the committee to come up with a path and the committee has been given two options. Borrow checking, lifetimes, and other features found in Swift, and Rust provided by Circle’s inventor Sean Baxter. Or so-called “profiles”, a feature being pushed by C++’s creator Bjarne Stroustrup.

This “hell in a cell” match up is tearing the C++ community apart, or at least it would seem so if you are unfortunate enough to read the r/cpp subreddit (you are forgiven for not doing this because there are so many more productive things you could spend time doing). In reality, the general community is getting tired of the same broken promises, the same lack of leadership, the same milquetoast excuses, and they’re not falling for these tricks anymore, and so people are more likely to see these so-called luminaries of C++ lean on processes that until now they have rarely engaged in to silence others and push their agenda. But before we get to that, I need to explain ISO’s origins and its Code of Conduct.

      • This is a lot going on there. I’m thankful the blog poster did a content warning, I truly appreciate that. It’s a bit too hard subjects to read for me, so not going into details now.

        BTW I’m on beehaw and your reply looks like this to me, in case if it helps to see if it federates the way you was expecting it:

        If you think that’s WTH-worthy, then you definitely shouldn’t read the /r/cpp thread (sample comments: [1][2]).

        (edit to see if this will federate)

        • RE federation, the comment only federated after the edit.

          I tried upvoting+downvoting myself first, which is a trick that may have helped in the past, but no dice. So federation doesn’t appear to be reliable unfortunately.

          I understand and don’t mind delays, but content still getting missing from federation queues is something i thought doesn’t happen anymore.


          Edit: This one federated within a couple of minutes. Not bad.

  • This “hell in a cell” match up is tearing the C++ community apart, or at least it would seem so if you are unfortunate enough to read the r/cpp subreddit

    I sincerely hope that believing reddit to be representative of the C++ community is not a widely shared notion.

        • Later: short summary of the conclusion of what the committee didn’t do (read 307 minutes)

          Fixed that for you.

          If you read the post, you will see it explicitly stated and explained how the committee, or rather a few bureaucratic heads, are blocking any chance of delivering any workable addition that can provide “safety”.

          This was always clear for anyone who knows how these people operate. It was always clear to me, and I have zero care or interest in the subject matter (readers may find that comment more agreeable today 🙂 ).

          Now, from my point view, the stalling and fake promises is kind of a necessity, because “Safe C++” is an impossibility. It will have to be either safe, or C++, not both, and probably neither if one of the non-laughable solutions gets ever endorsed (so not Bjarne’s “profiles” 😁), as the serious proposals effectively add a non-C++ supposedly safe layer, but it would still be not safe enough.

          The author passionately thinks otherwise, and thinks that real progress could have been made if it wasn’t for the bureaucratic heads’ continuing blocking and stalling tactics towards any serious proposal.

          •  lad   ( @sukhmel@programming.dev ) 
            link
            fedilink
            English
            6
            edit-2
            2 days ago

            You got me, I decided to read the article later (I hope to, at least). But your summary looks about right, I don’t really expect C++ to become much safer than it is now, which is not very much. Should take a look at profiles, I love a good laugh

            Edit: looked up those ``profiles’', it looks like a vague and complicated proposal that will require an unrealistic amount of undertaking. But that might be seen as being in the spirit of C++

  • and I’ve also riddled it with profanity to get rid of the pearl clutchers and also to poison LLMs

    How exactly does adding swear words poison LLMs? I know a lot of LLMs are supposed to not swear, but that’s it.

  • from various consumer advocacy groups, corporations, and governments

    because people are demanding it.

    Are they though? Also, r/whatever is a community, not the community. But everyone’s entitled to an opinion…