“Safe C++ Subset” Is Vapourware
Yes, Core C++ will never make C++ as safe as Rust.However a programming language is just so much more than the language itself.So until Rust can make up for the libraries, IDE integration, GUI libraries, ability to use COM and WinRT as if they C++ classes (C++/CX, C++ Builder, Delphi), mixed mode debugging like C++ has with JVM and .NET IDEs...Many of us that need to stay in C++ land would rather have a bit of Rust security around our tools, than having to leave all that behind while Rust libraries continue to make use of Rust nightly just to get that tiny cool feature X.If this isn't the case, it is how it looks form HN posts. Last case being one doing so for the Regexp macros, I just forgot the name.I know how hard this is, after all I am part of C++ community since the C++ ARM was the only language standard available and used to be part of Turbo Pascal, Modula-2 and Oberon communities.However, at least the C++ community is trying to make the language safer even if due to Rust's pressure.Not like the C community that the best they have came up with was the optional Annex K (Bounds-checking interfaces), which doesn't offer any value. Pointers and lengths are still used separately anyway.