This can be confusing as you can't tell which method is being called.
It also leads to a backwards compatability hazard for conditional trait methods, though these are currently alleviated by virtue of the trait being sealed.
Additionally, WrapErralso exposes anyhow compatibility methods like context, which leads to the same confusion and footguns in the other direction.
This has lead to misunderstandings, poor reasonability, as well as mistakes in code where we called the wrong method.
Consider making anyhow compatibility consistent under one trait.
This can be confusing as you can't tell which method is being called.
It also leads to a backwards compatability hazard for conditional trait methods, though these are currently alleviated by virtue of the trait being sealed.
Additionally,
WrapErr
also exposes anyhow compatibility methods likecontext
, which leads to the same confusion and footguns in the other direction.This has lead to misunderstandings, poor reasonability, as well as mistakes in code where we called the wrong method.
Consider making anyhow compatibility consistent under one trait.