“Hands-On With Abseil”
summary
Introduces Abseil as Google’s portable C++ library set with concrete compatibility rules: a target five-year support window, Bazel as the build truth with CMake coming, and an explicit no-dynamic-unload stance to avoid shutdown races. Shows practical APIs and tradeoffs: StrCat avoids repeated allocations and is ~10x faster than naive concatenation, StrSplit lifetime-extends temporaries so range-for works, and the new flags use atomics and locks for thread-safe flags with incremental migration paths.
AI-written summary · about
chapters (16)
- 0:00Intro
- 1:11Do you think the standard can live it head
- 4:23Standard library vendors dont wait for the standard
- 6:46Command line flags
- 12:45Library compatibility
- 19:03Naming
- 22:57Maintainability
- 29:22Abseil
- 29:48Nested namespaces
- 30:05Exceptions
- 32:10Compatibility Guidelines
- 34:27Global Scope Destruction
- 40:40Dynamic Unloading
- 42:18Compatibility Questions
- 48:39StirSplit
- 55:44ABsale
related talks
01h 18mAbstraction: The True Superpower of C++
40mLessons from two decades of writing bad code
01h 37mC++ And Beyond: Discussion
01h 00m“Evolving array_view and string_view for safe C++ code"
01h 13mPractical Production-Proven Constexpr API Elements
01h 29mC++ API & ABI versioning
32mC++ Standard Library "Little Things”
57mAbstraction: The True Superpower of C++