> These issues don't exist in languages that aren't built on a marsh. Unsafe casts exist in almost any GCed strongly typed language. You can unsafe things even

> These issues don't exist in languages that aren't built on a marsh. Unsafe casts exist in almost any GCed strongly typed language. You can unsafe things even in Rust, if you want to. Author of this code has deliberately made a choice to circumvent language's limitation and forgo it's guarantees. We have been doing it since undefined behaviour in C, how is that Typescript's fault?