error-chain
error-chain copied to clipboard
rust-lang-deprecated
Error boilerplate for Rust
Currently, they are not Sync because they contain a non-Sync trait object. This is a breaking change. The decision to make errors Send but not Sync was made in #110....
The failure crate requires that errors are `Sync`. Currently (but not in all previous versions) error-chain makes errors which are `!Sync` (because they have a `Box` inside them). It would...
Is there a way to get a string representation of the error chain without newlines? For example, this chain: ``` Error: decoding error Caused by: cannot decode message payload Caused...
On Windows, when appropriate feature is enabled, it would be cool to be able to run this kind of code when constructing a Error struct: if (unsafe { winapi::um::debugapi::IsDebuggerPresent() !=...
Possible syntax: ``` error_chain! { derive { Eq, PartialEq } ... } ``` We may have to add a trait which the chained errors would have to implement.
I noticed a small error in the documentation. `to_string` is not necessary when in the context of a `println!` call, because both `to_string` and the `{}` format specifier use the...
To avoid mistakes with programmers with little experience. It would be much more efficient to decide what to do with this crate and give alternatives. It forces you to understand...
Loving error-chain, thank you. Recently I wanted to chain errors returned by a thread. I ran into some difficulty and ended up with a [solution](https://stackoverflow.com/a/62823352/6844327). Not sure if you would...
https://travis-ci.com/rust-lang-nursery/error-chain/jobs/205173078 | 100 | Symbol::Dladdr(ref s) => return s.addr(), | ^^^^^^^^ expected enum `libc::c_void`, found enum `std::os::raw::c_void` | = note: expected type `core::option::Option` found type `core::option::Option` error[E0308]: mismatched types
Moving them out of bin would help us to reduce number of downstream changes in error-chain packaging in Fedora. Thanks!
