Crates.io | context-attribute |
lib.rs | context-attribute |
version | 1.0.0 |
source | src |
created_at | 2019-05-09 21:38:19.237855 |
updated_at | 2019-05-09 21:38:19.237855 |
description | Set the error context using doc comments. |
homepage | |
repository | https://github.com/yoshuawuyts/context-attribute |
max_upload_size | |
id | 133156 |
size | 30,430 |
Set the error context
using doc comments.
This is useful because instead of writing manual error messages to provide context to an error, it automatically derives it from doc comments. This works especially well for async contexts, where stack traces may not be persisted past yield points and thread boundaries. But contexts do.
use context_attribute::context;
use failure::{ensure, ResultExt};
/// Square a number if it's less than 10.
#[context]
fn square(num: usize) -> Result<usize, failure::Error> {
ensure!(num < 10, "Number was too large");
Ok(num * num)
}
fn main() -> Result<(), failure::Error> {
let args = std::env::args();
ensure!(args.len() == 2, "usage: square <num>");
let input = args.skip(1).next().unwrap().parse()?;
println!("result is {}", square(input)?);
Ok(())
}
$ cargo run --example square 12
Error: ErrorMessage { msg: "Number was too large" }
Square a number if it's less than 10.
$ cargo add context-attribute
This crate uses #![deny(unsafe_code)]
to ensure everything is implemented in
100% Safe Rust.
Want to join us? Check out our "Contributing" guide and take a look at some of these issues:
None.
MIT OR Apache-2.0