Remove anyhow from re_ros_msg and re_arrow_util#12702
Conversation
re_ros_msg and re_arrow_util`re_ros_msg and re_arrow_util
There was a problem hiding this comment.
Thank you for your PR! The motivation behind
is to have more structured error reporting that can replace the functionality provided by anyhow while allowing downstream processing. Yet this PR does not add any structure beyond the single variant ArrayComparisonError.
For example, I would expect an Error::ChildCountMismatch (or similar) variant in re_arrow_util. The ROS-related errors go into the right direction.
|
thank you for the feedback. originally, I focused on current usage; since no callers match on variants, I went for a simple unit struct I've added as many error variants as I deemed necessary, reducing further would lose meaningful distinctions, but I'm happy to hear your opinion if you disagree. |
Related
anyhowwiththiserrorin libraries #1845What
anyhowfrom public fns inutils/crates