> I miss absl::StatusOr

Sounds like you would rather have an `ErrorOr<User>` than a `Result<User, Error>`.

Both are union types wrapped in a monadic construct.

I wrote example above: https://news.ycombinator.com/item?id=46508392

My point is not the types/monadic constructs, etc (I love to do functional jerk off as a guy next to me, though), but that there are ways to keep code readable and straightforward without neither invocation chains

DoOne().OnError().ThenDoTwo().ThenDoThree().OnError()

nor coloring/await mess, nor golang-style useless error handling noise