Re:C++26 is done ISO C++ standards meeting, Trip Report
by Tenobrus on Sunday March 29, 2026 @04:57PM
(#47567230)
"Japanese soldier who kept fighting 29 years after World War 2"
[ Parent
| on HN ]
Re:C++26 is done ISO C++ standards meeting, Trip Report
by cedws on Sunday March 29, 2026 @05:02PM
(#47567279)
I watched a talk from Bjarne Stroustrup at CppCon about safety and it was pretty second hand embarrassing watching him try to pretend C++ has always been safe and safety mattered all along to them before Rust came along.
Re:C++26 is done ISO C++ standards meeting, Trip Report
by einpoklum on Sunday March 29, 2026 @05:52PM
(#47567776)
Well, there has been a long campaign against manual memory management - well before Rust was a thing. And along with that, a push for less use of raw pointers, less index loops etc. - all measures which, when adopted, reduce memory safety hazards significantly. Following the Core Guideliness also helps, as does using span's. Compiler warnings has improved, as has static analysis, also in a long process preceding Rust.
Of course, this is not completely guaranteed safety - but safety has certainly mattered.
Re:C++26 is done ISO C++ standards meeting, Trip Report
by cedws on Sunday March 29, 2026 @06:54PM
(#47568303)
>Following the Core Guideliness also helps
Yes, this what Stroustrup said and it makes me laugh. IIRC he phrased with a more of a 'we had safety before Rust' attitude. It also misses the point, safety shouldn't be opt-in or require memorising a rulebook. If safety is that easy in C++ why is everyone still sticking their hand in the shredder?
Re:C++26 is done ISO C++ standards meeting, Trip Report
by einpoklum on Monday March 30, 2026 @08:34AM
(#47573473)
You're "moving the goal posts" of this thread. Safety has mattered - in C++ and in other languages as well, e.g. with MISRA C.
As for the Core Guidelines - most of them are not about safety; and - they are not to be memorized, but a resource to consult when relevant, and something to base static analysis on.