Jake Goulding
Jake Goulding
Do you mean something like this, where the `Result` is created, the context is added, but then the `Result` is thrown away? ```ruby extern crate failure; use std::fs; use failure::{Context,...
My default suggestion is one per module. Things logically grouped together often have similar error cases.
Hmm. I'm not immediately thinking of any way to provide a better error message. The root problem is that the code is effectively: ```rust fn main() { let a: i32...
I don't know exactly what code changes would help improve the error message, but if someone finds it, we'd be happy to help it get merged!
Hmm. This feels like it could be similar to #99, another place where `AsErrorSource` isn’t valid (due to `’static`). There, I proposed being able to effectively disable the `Error::source` method,...
In general, there should be no inherent performance differences between `context` or `with_context`. Rust's optimizers pretty trivially improve the closure for `with_context`. The important thing to remember is that, most...
From @BurntSushi: > One thing that might help is being super clear in the docs what exactly is generated. I (stupidly, in retrospect) kept trying to call `fail` on a...
> This is also the first step toward #199, where custom context selectors will be needed. Can you explain a bit more about the general path you see? I don't...
It **is** enabled on docs.rs though. https://github.com/shepmaster/snafu/blob/6159ea9f3a3e189f1faa2f63904402f04dea54ec/Cargo.toml#L25 What do you propose as an alternate?