error-chain
error-chain copied to clipboard
rust-lang-deprecated
Error boilerplate for Rust
https://github.com/rust-lang-nursery/error-chain/blob/master/.travis.yml#L36 @alexcrichton Or remove the gh-pages handling
It is claimed these two concepts can be unified with specialization. I don't know what that entails.
https://github.com/rust-lang/rust/pull/44174 landed in rust nightly and now I have to add ``` impl From for Error { fn from(infallible: Infallible) -> Self { match infallible {} } } ``` to...
How to deal with multiple threads? Especially scoped thread pools are of interest to me. So far all attempts of implementation ended with ``` error[E0277]: the trait bound `std::error::Error +...
I have this function to print errors: ``` pub fn print_err(err: Error) -> T { println!("\n === \nError: {}", err); for e in err.iter().skip(1) { println!(" caused by: {}", e);...
I notice you were using hack of hidden attribute (#182, #193). I presume you will want to make use of non-exhaustive attribute when it becomes available, and I was wondering...
Currently backtraces are resolved immediately via `Backtrace::new` https://github.com/rust-lang-nursery/error-chain/blob/c9b37574d4cbcc1c27a1a72de928c77f447e56ac/src/lib.rs#L616 but the backtrace crate also supports constructing an [unresolved backtrace](http://alexcrichton.com/backtrace-rs/backtrace/struct.Backtrace.html#method.new_unresolved). Is there any reason why a resolved backtrace is constructed instead of...
I currently have error chain setup like this: ```rust /// main.rs use db; error_chain! { errors { DbRead { // ... } } } ``` ```rust /// db.rs error_chain! {...
This makes using `#![deny(missing_docs)]` impossible at the crate level. ``` error: no rules expected the token `;` --> src/error.rs:12:1 | 12 | / error_chain! { 13 | | foreign_links {...
My application uses the general Rust `log` crate, as well as lots of `error_chain`. I'd like to contribute a feature for this crate called `log`, which causes `quick_main!` to write...
