> Memory safety and "no undefined behaviors" (obviously untrue, but that was the belief and part of the conversation we had to have
Trying to better understand this claim, is it because also unsafe rust exists?
Trying to better understand this claim, is it because also unsafe rust exists?
It can be argued that those are bugs of the compiler, not the language (but in practice that doesn't matter, it's unsound in the only way that matters now!) and that it's very unlikely to be hit by accident (but someone can leverage it intentionally to cause unsoundness in their library, without the presence of unsafe).