From dad8c20f0c5662122270d0da862c64e46d657eff Mon Sep 17 00:00:00 2001 From: Harald Hoyer Date: Thu, 20 Dec 2018 16:50:36 +0100 Subject: [PATCH] Cargo update --- Cargo.toml | 10 +++++++++- README.md | 2 ++ 2 files changed, 11 insertions(+), 1 deletion(-) diff --git a/Cargo.toml b/Cargo.toml index 41f0011..ac13816 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -3,9 +3,17 @@ name = "chainerror" version = "0.1.0" authors = ["Harald Hoyer "] edition = "2018" +license = "MIT" +documentation = "https://docs.rs/chainerror" +homepage = "https://haraldh.github.io/chainerror/" +repository = "https://github.com/haraldh/chainerror" +description = "Yet another error boilerplate library." +keywords = ["error"] +categories = ["rust-patterns"] +readme = "README.md" [features] default = [ ] no-fileline = [] display-cause = [] -no-debug-cause = [] \ No newline at end of file +no-debug-cause = [] diff --git a/README.md b/README.md index ea5a7ff..c4e426c 100644 --- a/README.md +++ b/README.md @@ -3,6 +3,8 @@ `chainerror` provides an error backtrace like `failure` without doing a real backtrace, so even after you `strip` your binaries, you still have the error backtrace. +`chainerror` has no depenendencies! + `chainerror` uses `.source()` of `std::error::Error` along with `line()!` and `file()!` to provide a nice debug error backtrace. It encapsulates all types, which have `Display + Debug` and can store the error cause internally.