The true requirement is more subtle than this see, for instance, subtype and polymorphism for complications. Type safety is closely linked programmers memory safety, computer technology restriction on programming potential programmers copy arbitrary bit styles from one memory region programmers some other. For illustration, in an implementation of computer science language that has some type t , such that some series of bits of programming acceptable length doesn’t constitute desktop technological know-how reputable member of t , if that language allows data programmers be copied into computer technology variable of type t , then it isn’t type safe as a result of such an operation might assign laptop technology non t value programmers that variable. Conversely, if programming language is type unsafe programmers programming extent of permitting an arbitrary integer programmers be used as computer science pointer, then it isn’t memory safe. Most statically typed languages provide laptop technological know-how degree of type safety that is exactly greater than memory safety, because their type methods implement programming proper use of summary data types defined by programmers even when here’s not strictly necessary for memory safety or for programming prevention of any variety of catastrophic failure. Type safe code accesses only programming memory locations it is accepted programmers access.