Hot take: most people don't care about memory safety. It's "just" another type of bug.
-
-
-
I think you may be right, but people should be honest about that instead of pretending that modern C++ is memory-safe.
- 1 more reply
New conversation -
-
-
I wouldn't group C and modern C++ in the same token. C++ is by no means a safe language, but the overlap between its problems and C's is getting smaller by the year (std::string and smart pointers help dramatically, but references introduce a whole new hell)
-
Modern C++ is less safe than C.
- 3 more replies
New conversation -
-
-
How much hope do you hold out for static analysis tools to make it possible?
-
None. C++ cannot be made memory-safe without sacrificing so much compatibility as to make it not C++ anymore.
- 4 more replies
New conversation -
-
-
Agreed. I have never seen any coder able to do it, no matter how much experience or chops they have.
-
That makes me a bit sad, still have C/C++ as a goal to add to my list of languages I code in.
- 9 more replies
New conversation -
-
-
I hate to disappoint you, but I am most likely human and I wrote many lines of memory-safe C/C++ for many years. I would have no problem returning to C but I would now choose not to use C++.
-
Given the nature of memory bugs I don't think anyone can say "I write memory-safe code". What tools did you use to prove that it was safe, that it didn't trigger any UB and that no mistake was done because of an obscure part of standard? Just curious.
- 19 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.