| Crates.io | err_trail |
| lib.rs | err_trail |
| version | 0.8.5 |
| created_at | 2024-12-06 15:27:32.551055+00 |
| updated_at | 2024-12-28 18:39:19.990536+00 |
| description | Add context to errors through logging |
| homepage | |
| repository | https://github.com/mcmah309/error_set |
| max_upload_size | |
| id | 1474380 |
| size | 66,517 |
Convience methods on Result and Option for logging when an Err or None is ecountered. Similar to anyhow
but for logging.
tracing / log / defmt :
Enables support for the tracing or log or defmt crates. Methods are added to Result and are executed when the Result is an Err for logging purposes. They work similarly to anyhow's .context(..) method. e.g.
let result: Result<(), &str> = Err("operation failed");
let value: Result<(), &str> = result.error_context("If `Err`, this message is logged as error via tracing/log/defmt");
let value: Result<(), &str> = result.warn_context("If `Err`, this message is logged as warn via tracing/log/defmt");
let value: Result<(), &str> = result.with_error_context(|err| format!("If `Err`, this message is logged as error via tracing/log/defmt: {}", err));
let value: Option<()> = result.consume_as_error(); // If `Err`, the `Err` is logged as error via tracing/log/defmt
let value: Option<()> = result.consume_with_warn(|err| format!("If `Err`, this message is logged as warn via tracing/log/defmt: {}", err));
// ...etc.
This is useful tracing context around errors. e.g.
let val = func().warn_context("`func` failed, here is some extra context like variable values")?;
let val = func().consume_as_warn();
rather than
let val = func().inspect_err(|err| tracing::warn!("`func` failed, here is some extra context like variable values"))?;
let val = func().inspect_err(|err| tracing::warn!("{}", err)).ok();
Note: a
stubfeature flag also exists to be used by libraries. This allows the api's to be used in libraries while a downstream binary can ultimately decide the implementation. If no implementations is selected, since all the above methods are inlined, the code will be optimized away during compilation.
warn - Represents a bad state in which the current process can continue.
error - Represents a bad state in which the current process cannot continue.
Result to the calling function, context should usually be warnResult, context should usually be error