anyhow (Rust crate)

“Rust's anyhow crate was able to square this circle by adding a blanket trait impl for Context”

“you are not supposed to expose errors from a library with anyhow, they are only for application/top level code”

“I've never had a problem using anyhow to pass errors up the call stack in any project I've used it in.”

“if a library ever exposes that, then that's just the author being lazy and not doing errors correctly”

“Anyhow and thiserror are a cinch.”

“If a crate exposes `anyhow::Error`, that's a lazy choice and bad API design”

“thiserror and anyhow are std::error::Error with fewer steps.”

“Anyhow mostly works but this is approximately as verbose as the Go error handling”

“Anyhow is perhaps the closest one to another paradigm because it allows you to discard typed information in favor of just the string messages”

“I use anyhow for this, so I should also add "add context to an error when I fall" to the list of things I do.”

“Or just go with Anyhow until you find a need for something else.”

“Rust has three main error systems (io::Error, thiserror, and anyhow), which is a pain”

“anyhow and syn are literally from a core Rust dev”

“Even with anyhow there is a lot of boilerplate it seems to me dealing with crates that don't use it.”

“exn can use anyhow::Error as its inner Error”

“Rust already has a head start compared to most other languages with Result, expect and anyhow”

“If one skips that part and opts for anyhow because it's too much work, that's really a user problem.”

“anyhow for applications, thiserror for libraries.”

“most of them are favorable (or not unfavorable) to anyhow”

“I usually use `anyhow` to do that for me”

“something like anyhow for applications”

“it’s so much less friction, and much better than just doing panic”

“anyhow seems useful in the very top layers where you basically just want bubble the useful errors modeled elsewhere”

“either a third party dependency (anyhow) that mimics Go's errors stdlib package”

“they all get abandoned sooner or later, and they brought very little to the table”

“The pros for using anyhow are big: Easily stack errors together”

“just use anyhow with .context”

“using eyre or anyhow or other error context libraries build convenient error context backtraces without needing to format things oneself”

“I believe `anyhow` can mostly do the same.”

“the standard convention if you just want a stringly-typed error like Go is anyhow?”

“Use thiserror to make error types in libraries, and anyhow in programs to handle them.”

“you can use things like anyhow or error_context to add context before returning”

“Just anyhow macro wrap your errors and just log them out.”

“this gets things done, but I'm told not to expose these errors in my public API”

“goes a long way to being able to fail fast and return an Err rather then panicking”

“Anyhow is a great thing to get you started.”

“It keeps the size of Result down by limiting the 'E' to be a pointer.”

“anyhow::Error (or similar) seems poised to become idiomatic in Rust, which AFAIU always allocates”

“No matter what error we put into an anyhow::Error, the stack size is 8 B.”

“especially with crates like anyhow and thiserror”