No. It is memory dangerous. Please use appropriate personal protective equipment when using this, or you may find you have lost all memory of your family. More

No. It is memory dangerous. Please use appropriate personal protective equipment when using this, or you may find you have lost all memory of your family. More seriously: no, it makes no guarantees, but it tends to a much safer style by default: Bounds are checked, raw pointer arithmetic is ugly, clunky, and rarely used (although useful within, eg, the memory allocator), implicit conversions are gone, and null pointers aren't present in either the language or the library. You can define your own, even in a generic manner, but nothing uses this ability. Uninitialized variables are generally a compile time error (barring some bugs in the data flow analsyis), and so on. You can poke holes in the type system, but these holes are explicit. As a result, most code written is going to be far safer than, say, C.