Post #4029874

@cwebber@social.coop Just one nitpick: pretty much every GCd language has mechanisms to interact with pointers and muck around with types. The same capabilities from Rust's unsafe are generally available (except for fully sandboxed VMs, but that's not a property of the language), and depending on the prevalence of native modules in an ecosystem, their use can be quite extensive. Go and Java tend to reimplement natively, Python tends to FFI, for example. This is not to discount the benefits of a GC, but rather to point out that in general people haven't argued that those languages *aren't* memory safe despite the existence of torn reads or specialized APIs that can cause memory safety. Something like invisicaps/Fil-C or WASM sandboxing of an application and its dependencies would be a more complete solution than what most runtimes provide, of course.