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.
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”
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.
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”
At least it’s not like Russia, where it’s “plz don’t fall to your death, if you do it’s our fault”…
I thought a lot of places are like that, that’s why we get all the fences and such 🤔
Maybe a “pragma strict” where every deprecated is an error and not a warning?