this post was submitted on 17 Sep 2024
2 points (100.0% liked)

C++

2040 readers
2 users here now

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

Rules

founded 2 years ago
MODERATORS
lysdexic@programming.dev
Nihili0@programming.dev
2
The empire of C++ strikes back with Safe C++ blueprint (www.theregister.com)
submitted 9 months ago* (last edited 9 months ago) by cmeerw@programming.dev to c/cpp@programming.dev
25 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] FizzyOrange@programming.dev 0 points 9 months 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 1 points 9 months ago

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"

[–] bufalo1973@lemmy.ml 1 points 8 months ago

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