this post was submitted on 31 Mar 2025
9 points (84.6% liked)

C++

1944 readers
1 users here now

The center for all discussion and news regarding C++.

Rules

founded 2 years ago
MODERATORS
 

This is a status update on improvements currently in progress for hardening and securing our C++ software.

top 4 comments
sorted by: hot top controversial new old
[–] [email protected] 8 points 4 days ago (1 children)

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.

[–] [email protected] 3 points 4 days ago

Yeah I would estimate something like 0.5%.

[–] [email protected] 4 points 4 days ago

Maybe if we just add even more things to C++ then it will finally become the perfect language for all purposes for all time!

[–] [email protected] 8 points 4 days ago

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.