error-chain
error-chain copied to clipboard
rust-lang-deprecated
Error boilerplate for Rust
I get an error from error_chain!{} which origins outside of my crate: ``` error: no rules expected the token `ERROR_CHECK` --> lib/core/libimagstore/src/error.rs:20:1 | 20 | / error_chain! { 21 |...
error: recursion limit reached while expanding the macro `quick_error` based on number of ErrorKinds
This is similar to #91, but more concrete. I'm using 1 foreign link and 8 errors, like so: ```rust error_chain! { types { Error, ErrorKind, ResultExt, Result; } foreign_links {...
There are a lot of deficiencies with the current syntax that are pretty hard to resolve as a macro_rules macro: - Make it possible to attach attributes to Error and...
I'm having a problem with `dotenv` which uses both `error-chain` and `error-chain-derive`: https://github.com/slapresta/rust-dotenv/issues/65 This isn't a specific problem of `dotenv`, but any library that uses `error-chain` and `error-chain-derive` as a...
It would be neat if this crate worked with `#![no_std]`. The main thing it's using seems to be `Box`, which could use `collections` in a `no_std` context. If there's interest...
The following code shows a reasonably written error type by a library not using error chain, as well as a chained error containing that one as a variant. ```rust #[macro_use]...
This macro was copied from the quick_error crate and hacked up to fit into error_chain. It actually supports syntax that error_chain doesn't use. It needs to be simplified to do...
There are two big examples in this crate - the one in the crate-level docs, and the one in the `example_generated` module; and they are not the same. Make them...
The backtrace crate is < 1.0 so error-chain can't hit 1.0 without either bumping backtrace or encapsulating it. It looks like the out-of-crate Backtrace type is already encapsulated, but BacktraceFrame...
If a module exports `Error` and `ErrorKind`, then it could be great to be able to write the following ~~~ rust error_chain! { links { Mymodule(my_module); } } ~~~ This...
