this post was submitted on 17 Sep 2024
36 points (95.0% liked)

C++

1763 readers
1 users here now

The center for all discussion and news regarding C++.

Rules

founded 1 year ago
MODERATORS
Nihili0@programming.dev
lysdexic@programming.dev
36
The empire of C++ strikes back with Safe C++ blueprint (www.theregister.com)
submitted 1 month ago* (last edited 1 month ago) by cmeerw@programming.dev to c/cpp@programming.dev
38 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] GetOffMyLan@programming.dev 13 points 1 month ago (1 children)

All the use after free and buffer overflow bugs that plague our key infrastructure.

[–] FizzyOrange@programming.dev 7 points 1 month ago (2 children)

It's not just that. Debugging segfaults and UB can be an absolute nightmare.

The C++ committee still haven't learnt their lesson. I recently learnt about C++20 coroutines, which are pretty neat, if complex (there are pretty much no good learning resources about them). However they are still putting unnecessary UB footguns in it.

[–] sukhmel@programming.dev 4 points 1 month ago (1 children)

Reminds me of how I found some safety measures to be in China some years back, basically those were signs saying "plz don't fall to your death, if you do it's your fault"

[–] lambalicious@lemmy.sdf.org 1 points 1 month ago (1 children)

At least it's not like Russia, where it's “plz don’t fall to your death, if you do it’s our fault”...

[–] sukhmel@programming.dev 2 points 1 month ago

I thought a lot of places are like that, that's why we get all the fences and such 🤔

[–] bufalo1973@lemmy.ml 1 points 1 week ago

Maybe a "pragma strict" where every deprecated is an error and not a warning?