For the first time I'm seriously dealing with #rust Errors.
The situation is that my son and I built a little library that has to deal with several other libraries:
#serde_json
#lapin
#deadpool
and all these libraries introduce their own Errors.
Our lib is made to allow for data processing that also introduces its own errors.
And now, once the data processing is engaged, the results of it have to be communicated to the outer world. Lots of different Errors might have happened in the rather complicated processing path the whole processing chain travels along.
This was the reason I initially opted out for a simple and unique Error type, that is String.
Then came the translation issues, because the outer world might want to interpret the errors in its own language, so the String Error type is not an option any more.
All things said, I'm grateful for #rust's match. The whole complication introduced by dealing with all sorts of Errors actually helps me in understanding how our lib works.
And our little library will end up as a not so little library, as it seems.