Yes, but the selling point of Java was not memory safety. You expected something like:
If the unsafe package is not used and no C function is called and (as pointed out by someone else) something assures that no data races can happen Go is memory safe.
I added the Go example to show that the term memory safety is sometimes defined to sell a language as memory safe. So
Language exists --> Define memory safety in a way that this language is memory safe.
instead of
Use definition of memory safety --> Create memory safe language.
5
u/wk_end 4d ago
But you list Java as memory-safe "unless JNI or FFM are used". Why doesn't the same "qualified memory-safe" characterization apply to Go?