AMA with Herb Sutter - Meeting C++ live

Herb Sutter joined us for an extended AMA session on his various C++ roles, he talks about C++26, safety, reflection, Cpp2, Rust, C++ committee process and proposals. In his keynote at Meeting C++ 2024 he will be peering forward into C++'s next decade:
meetingcpp.com...

[@eotcoldhymns2930]

Long live Herb Sutter

[@Roibarkan]

6:06 In fact the cpp2 subscript checks are not just for contiguous containers, but for all sized ranges (herbs touches some of this on 45:45).

[@Roibarkan]

30:57 Titus Winters on language evolution (pacific++ 2018): kzbin.info/www/bejne/f4qbpXueZ7GGjpYm16s

[@nirajandata]

👀👀

[@juanag7908]

No networking yet And also C++ is not late to memory safety, ¿really? ¿is this a joke? And the parts that "it is fine being on fire" because there is more C++ being code than Rust is just blowing my mind, thats explains a lot of the current status of C++ and it future And what it is worst, the focus is on memory safety as it is the only issue when it is one of many, i moved to Rust after 15 years because of memory safety but i was trying other options because C++ complexity is HUGE and out of scale and i hate with all my will CMake. If C++ ecosystem were as good as Rust is i will never even tried Rust in the first place So memory safety is a patch, more and more industries will move away from C++ if the above dont improve and fast, and honestly, i had used C++ hardcode for 15 years and more i know the ISO is going to screw somehow, they always do, profiles will be kind of a disaster, 0 clues but also 0 doubts, it is always like that Is sad seeing in real time how C++ becomes a legacy lang day by day