C++ is not memory-safe and cannot be coerced into being so.
You can write nice C++ in the C++14 style, but you can't turn off or ban the unsafe features. Until I can make my program fail to compile if there is a bare pointer in it (and how would that work with the standard library and system API?), it's not a memory-safe language.
There isn't any definition of memory safe, nor any published version of C++, for which this is a true claim.
Re:I missed Nim (2014)
by steveklabnik on Thursday January 21, 2016 @04:25PM
(#10948502)
> Those requirements contradict themselves in numerous ways
I'd be interested in hearing more about how.
Those requirements contradict themselves in numerous ways. As always, engineering tradeoffs are paramount.
As for "statically typed, memory safe, no VM" -- C++ fits all those perfectly. (Provided you put in the effort of learning C++. There's another tradeoff you'd need to keep in mind.)