The problem is with defining what a “memory safety violation” is. By the time you’ve annotated all the code with the information necessary to tell what you find

The problem is with defining what a “memory safety violation” is. By the time you’ve annotated all the code with the information necessary to tell what you find undesirable up to rust’s capacity (e.g. overstepping buffers, violations of move semantics…), say through a type system that allows you to express these requirements, and have spent the time to change the parts of the program that did not fit with your new more restrictive types… … well congratulations, you’ve just written your program in a language that effectively is rust.