That's not quite right though, is it? Nothing prevents one from "creative" interpretation of memory in, say, C, either, but it would be difficult to argue C is untyped.
The C type system prevents you from accidental creative interpretation of memory. You wouldn't say Rust is untyped just because of the `unsafe` keyword either.
No such type safety exists in assembly, except that certain opcode-register combinations are prohibited.
No such type safety exists in assembly, except that certain opcode-register combinations are prohibited.