Get the latest tech news
There is no memory safety without thread safety
Memory safety is all the rage these days. But what does the term even mean? That turns out to be harder to nail down than you may think. Typically, people use this term to refer to language...
When that happens, we will run the Ptr version of get, which will dereference the Int ’s val field as a pointer – and hence the program accesses address 42, and crashes. This comes at a significant cost, restricting the language to never assume consistency of multi-word values and limiting which optimizations the compiler can perform. Even experienced Go programmers do not always realize that you can break memory safety without using any unsafe operations or exploiting any compiler or language bugs.
Or read this on Hacker News
