Mind your language

[OliverBr]

What about viewtopic.php?p=973106#p973106

Yes. That was a bug (albeit without consequences). So there is undefined behavior... from the programmer
But also from the compiler, because I never got a warning (or used the wrong options).
I guess there are more bugs in the code.
There is a nasty a with TT-hashtables and repetition. But this has little to do with the programming language, because it also happens in the Java version of a OliThink.

Of course, Java is quite strict on those undefined behaviors. Uninitialized variables are not allowed, you don't have access to free pointers and access to arrays is being checked with IndexOutOfBoundExcpetions thrown.

[jdart]

I don't find C++'s not being memory-safe to be a problem. The last time I had any memory-related issue like a buffer overrun was quite a while ago. If you use std::array, you get built-in bounds checking. And if you use scoped objects to contain allocated memory, then the memory can be freed automatically when you exit the scope. C++ doesn't enforce these patterns, but it supports them. Still, there are applications for which greater safety is important. This is one reason Java is popular for enterprise applications, and is also the reason Microsoft went to C# for much of its code.

I personally find Rust annoying for several reasons, one of them being that the memory ownership features add additional safety, but at the price of complexity for the programmer.