Abseil
Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.
4recommend
1warn against
Jan 5, 2026first mention
Jun 26, 2026latest mention
Why people recommend it
“Abseil has the convention where instead of assert(), users call”
Show 1 more
“b-tree maps hold multiple values per node, which makes them more cache-friendly than the red-black trees used in std::map”
Caveats and dissent
“without living in the world of abseil”
Threads where it came up
- Lessons from Hash Table Merging 2 mentions
- A C++ implementation of a fast hash map and hash set using hopscotch hashing 1 mention
- The Fastest Linux Timestamps 1 mention
- C++26: A User-Friednly assert() macro 1 mention
- Clang/LLVM static analyzer that detects microarchitectural hazards 1 mention
- Banned C++ Features in Chromium 1 mention
Data: abseil.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 9
“Abseil Swiss Tables carefully avoids intermediate allocations/copy constructor calls.”
“which I thought is a neat trick”
“Abseil has the convention where instead of assert(), users call”
“I ran it against Abseil.”
“without living in the world of abseil”
“Yes, so it is with Abseil. The default rust hash functions, siphash in the standard library and foldhash in hashbrown, are ~3X as slow”
> HashMap implements Extend, so just h0.extend(h1) and you're done, the people who made your HashMap type are much better equipped to optimize this common operation. Are you sure? I'm not very used to reading Rust stdlib, but this seems to be the implementation of the default HashMap extend [1]. It just calls self.base.extend. self.base seems to be hashbrown::hash_map, and this is the source for it's extend [2]. In o
“b-tree maps hold multiple values per node, which makes them more cache-friendly than the red-black trees used in std::map”
Is this similar? https://github.com/amantinband/error-or What's some of the "preprocessor magic" that makes this[1] more ergonomic to use? [1]: https://github.com/abseil/abseil-cpp/blob/master/absl/status/statusor.h