C++ Committee's Library Evolution Working Group Panel
summary
Panelists map short-term freestanding direction to paper p0829 and flag the single most likely C++23 change as language-level removal of required operator new. Networking TS ships without TLS today and the group warns that adding encryption to the standard is both a technical and vendor/legal headache; recommendation is to use azure (an open-source superset) for now. Expect library modules and coroutine support per p0592, low odds for expected in C++23 but ~75% by C++26, ABI constraints block Unicode/regex changes and complicate cryptography and container redesigns.
AI-written summary · about
chapters (17)
- 0:00Introductions and disclaimer
- 2:34Favorite C++20 features
- 4:50Freestanding C++ direction
- 6:28Networking and encryption
- 10:57Standard encryption library
- 15:01Unicode and string ABI
- 18:13C++20 deadlines and decisions
- 22:00Future of std::expected
- 24:03ABI and library performance
- 29:00Embedded C++ developments
- 34:05Standard package management
- 38:48Recent ABI breakages
- 41:52Committee culture and shirts
- 43:25Standardizing compiler tools
- 48:06New STL implementations
- 52:35Stability vs progress
- 56:43Committee recognition and closing
related talks
01h 14m"Technical Specifications & C++17"
01h 35mISO C++ Standards Committee Panel Discussion 2024
01h 26mGrill The Committee Panel
01h 25mGrill the C++ committee
33mMSVC C++20/23 Update
01h 03mFreestanding C++ - Past, Present, and Future
01h 37mC++ And Beyond: Discussion
22mWhat happened to...: Deprecated and Removed Features of C++