Go error wrapping without the head-scratching
One letter in a format string decides whether the check you wrote yesterday still works today. Here's the whole of Go's error chain, built up from that letter, with every output taken from a real run.

One letter in a format string decides whether the check you wrote yesterday still works today. Here's the whole of Go's error chain, built up from that letter, with every output taken from a real run.

The job told me, very politely, that it hadn't done its job, and then exited 0. Two questions were enough to undo the spec written to fix it.

Leaving a healthy dependency: cockroachdb/errors predates Go 1.20, so its Join hides the aggregate and everything below it goes missing.

Adding stream-copy remux to a WebAssembly FFmpeg build, where writing Matroska hung forever and the identical MP4 path did not.

Go funnels errors through a handler. In Rust, diagnostics carry their own code and help and propagate on their own, so the funnel disappears.

Recovery advice belongs in a structured error hint, not buried in the message string. One error handler then decides how to show it.
