mirror of
https://github.com/haraldh/chainerror.git
synced 2024-10-05 20:15:11 +02:00
33 lines
994 B
Markdown
33 lines
994 B
Markdown
# Simple Chained String Errors
|
|
|
|
With relatively small changes and the help of the `cherr!` macro of the `chainerror` crate
|
|
the `String` errors are now chained together.
|
|
|
|
Press the play button in the upper right corner and see the nice debug output.
|
|
|
|
~~~rust
|
|
{{#include ../examples/tutorial2.rs}}
|
|
# #[allow(dead_code)]
|
|
# mod chainerror {
|
|
{{#rustdoc_include ../src/lib.rs:-1}}
|
|
# }
|
|
~~~
|
|
|
|
### What did we do here?
|
|
|
|
~~~rust,ignore
|
|
{{#include ../examples/tutorial2.rs:13:15}}
|
|
~~~
|
|
|
|
The macro `cherr!(olderror, newerror)` stores `olderror` as the source/cause of `newerror`
|
|
along with the filename (`file!()`) and line number (`line!()`)
|
|
and returns `newerror`.
|
|
|
|
`Err()?` then returns the inner error applying `.into()`, so that we
|
|
again have a `Err(Box<Error + Send + Sync>)` as a result.
|
|
|
|
The `Debug` implementation of `ChainError<T>` (which is returned by `cherr!()`)
|
|
prints the `Debug` of `T` prefixed with the stored filename and line number.
|
|
|
|
`ChainError<T>` in our case is `ChainError<String>`.
|