ohno crate was designed with the idea that, by default, an error message should contain all the information you might need to understand what went wrong.
Right now it prints:
- its own message
- inner error message
- enrichment
- backtrace
this is not compatible with the way most other errors in the Rust ecosystem are implemented. In general, they only print their own top-level message. As a result, when ohno errors are combined with errors from other crates, the final displayed message ends up stopping at the first third‑party error.
A potential solution might be to align with common Rust practices: print only the top-level message in impl Display, and additionally provide a method (e.g. full) that preserves the current behavior
ohnocrate was designed with the idea that, by default, an error message should contain all the information you might need to understand what went wrong.Right now it prints:
this is not compatible with the way most other errors in the Rust ecosystem are implemented. In general, they only print their own top-level message. As a result, when
ohnoerrors are combined with errors from other crates, the final displayed message ends up stopping at the first third‑party error.A potential solution might be to align with common Rust practices: print only the top-level message in
impl Display, and additionally provide a method (e.g.full) that preserves the current behavior