Matthias Beyer
dc162cb167
When printing the error chain, we print the error and then iterate over the causes. Hence, we have to increase the printed number by one here, because 0 (zero) is already printed. Signed-off-by: Matthias Beyer <mail@beyermatthias.de> |
||
|---|---|---|
| .. | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
libimagerror
In imag, we do not panic.
Whatever we do, if we fail as hard as possible, the end-user should never ever
see a backtrace from a panic!().
Anyways, the user might see a error trace generated by imag.
That is because imag is software for power-users, for nerds (I use the term
"nerd" because for me it is a good thing - I do not want to offend anyone by
using it).
This target group can read backtraces without getting confused. IO Error and
Permission denied Error are things that nerds can understand and they already
know what to do in the most obvious cases (such as Permission denied Error).
This library crate is for generating error types and handle them in a nice way.
It can be seen as mini-framework inside imag which was written to work with
error types in a specified way. All imag crates must use this library if they
can return errors in any way, except the libimagutil - which is for the most
basic utilities.