4 ms·
As far as I can tell, this bug has nothing to do with memory-safety. And I don't think C++ is to blame here. It's just a lot of untested code. Surely even Ocam
by petters 10y ago
As far as I can tell, this bug has nothing to do with memory-safety. And I don't think C++ is to blame here.
It's just a lot of untested code. Surely even Ocaml and Haskell need tests.
- yjgyhj 10y agoYes, this bug is not about memory safety - but having the state-writing operator so easy at hand was probably what lead to the mistake in the first place. In my GP comment I went on to rant about other classes of bugs which are obsolete since the 1970s, but still happen.
- willtim 10y agoNo C++ is to blame. This type of error could never happen in OCaml and Haskell.