We have already accomplished a great deal. Compile-time C++ is already fully free of UB, which means a huge chunk of real-world C++ is already UB-free today.
This statement is so categorically ridiculous that I have no choice but to assume that Herb Sutter is deliberately trying to mislead people. I would be very surprised if even 5% of "real-world C++" occurred at compile time. In fact, I would be very surprised if even 5% of "real-world C++" was valid constexpr that just ran at runtime.
News at 11: Senior C++ committee member still does not understand what memory safe means.
Seriously: C++ does not "archive parity with other memory-safe languages" (emphasis mine) since it is not a memory safe language itself, even if profiles deliver on everything they promise today.
4 Comments
0xDEADBEEFCAFE@programming.dev · 10 pts · 1y
This statement is so categorically ridiculous that I have no choice but to assume that Herb Sutter is deliberately trying to mislead people. I would be very surprised if even 5% of "real-world C++" occurred at compile time. In fact, I would be very surprised if even 5% of "real-world C++" was valid
constexprthat just ran at runtime.FizzyOrange@programming.dev · 3 pts · 1y
Yeah I would estimate something like 0.5%.
hunger@programming.dev · 9 pts · 1y
News at 11: Senior C++ committee member still does not understand what memory safe means.
Seriously: C++ does not "archive parity with other memory-safe languages" (emphasis mine) since it is not a memory safe language itself, even if profiles deliver on everything they promise today.
bitcrafter@programming.dev · 5 pts · 1y
Maybe if we just add even more things to C++ then it will finally become the perfect language for all purposes for all time!