We see no realistic path for an evolution of C++ into a language with rigorous memory safety guarantees that include temporal safety.
A large-scale rewrite of all existing C++ code into a different, memory-safe language appears very difficult and will likely remain impractical.
Tough spot to be in, but I’m glad there are more and more people calling out for a transition away from C/C++. One can only hope that Rust doesn’t become the new C++ aka the garbage dump of programming languages. Every large player wanted to write C++ in their own way, so they added it to the language and now we have this… thing.
Unfortuately c++ interoperability is hard. I wouldn’t write c++ without vector and other containers (templates). Or classes complete with inheiritance (rarely multiple) and thus name mangeling. I now have millions of lines of that stuff and it is hard to write anything else because it has to mix.
Tough spot to be in, but I’m glad there are more and more people calling out for a transition away from C/C++. One can only hope that Rust doesn’t become the new C++ aka the garbage dump of programming languages. Every large player wanted to write C++ in their own way, so they added it to the language and now we have this… thing.
CC BY-NC-SA 4.0
In the long run, I wonder if rust will spawn a family of new memory-safe languages.
Statically typed, compiled, memory safe languages? I can live with that 👌
CC BY-NC-SA 4.0
Unfortuately c++ interoperability is hard. I wouldn’t write c++ without vector and other containers (templates). Or classes complete with inheiritance (rarely multiple) and thus name mangeling. I now have millions of lines of that stuff and it is hard to write anything else because it has to mix.