imag/libimagerror at fc6cf0c709e3875a592aa46d9bc10fc5d962b370 - matthiasbeyer/imag

History

mario 8df5519f34 Move `[profile.dev] codegen-units = 2` to top-level Cargo.toml lower level (=package/crate level) definitions for profiles are ignored		2017-01-19 20:08:51 +01:00
..
src	Simplify `OnErr` iterator `next` and `next_back`	2016-10-21 11:03:02 +02:00
Cargo.toml	Move `[profile.dev] codegen-units = 2` to top-level Cargo.toml	2017-01-19 20:08:51 +01:00
README.md	Create symlinks to documentation files in libimag*/README.md	2016-10-13 12:04:36 +02:00

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.