absl

Google C++ bans exceptions and the main mechanism for propogating errors is `absl::Status` which the caller has to check.

It includes core cleanup (bye bye Folly, hello absl), a modular transport layer, and better ergonomics for real-world apps.

Of course, absl tables will have been improved since 2022, but there are many competitors that have improved as well.

It'd be stuff like the lock contention monitoring that the (C++) `absl::Mutex` has.

In c++ this plays out in libraries like absl, folly, boost and others.

The absl tables (the canonical Swisstables) are good, but not the fastest.

You should probably use either boost::unordered_flat_map or absl::flat_hash_map if you don't need ordering.

Example: absl::StatusOr<User> loadUserById(int userId) {...

> I miss absl::StatusOr Sounds like you would rather have an `ErrorOr<User>` than a `Result<User, Error>`.

I was hoping absl::Cleanup would get a shoutout.

I've been working with Rust more recently, and thinking through its error handling ecosystem led me down a rabbit hole comparing it to what I'd used before — C, Go, exceptions, and Google's Absl Status.

The highest-confidence finding is ThreadIdentity in absl/base/internal/thread_identity.h: three atomics (ticker, wait_start, is_idle) sharing a cache line, confirmed across 36 TUs, with a compound hazard (cache spanning + false sharing + wide write surface) on the same struct.

For C++ there are Boost, Folly, Absl, several more large libraries with reputable orgs behind them.