Jake Goulding comments

Results 615 comments of


                                            Jake Goulding

Consider how to support tuple variants

My current thinking is to make tuple variants effectively equivalent to this: ```rust #[derive(Debug, Snafu)] enum Error { #[snafu(context(false))] OneWay { source: AnError }, SameThing(AnError), } ``` That is, a...

Make backtrace output more end-user friendly

Hmm, I don't have a great answer to the _why_, but the good news is that soon this will become moot: ```rust use snafu::prelude::*; #[derive(Debug, Snafu)] struct NeatError { backtrace:...

Using `Self` in a context selector ends up referring to the selector, not the error type

I suppose we could scan for `Self` ourselves and emit our own more precise error...

Extension trait for Sink

That seems reasonable. I was under the impression that `Sink`s were semi-deprecated, which is why I didn't add support for them originally. General shape of how this would work: 1....

Can I use `context` for any error type that implements a trait without providing an exhaustive list of all possible source error types?

You should be able to using `source(from)`. Can you check the [relevant section of the guide](https://docs.rs/snafu/0.4.2/snafu/guide/attributes/index.html#transforming-the-source) and see if that solves your problem?

Can I use `context` for any error type that implements a trait without providing an exhaustive list of all possible source error types?

/cc #104

Can I use `context` for any error type that implements a trait without providing an exhaustive list of all possible source error types?

If that section of the guide helps you, I'd appreciate any feedback on making it easier to discover. All the documentation I could write will be useless if no one...

Can I use `context` for any error type that implements a trait without providing an exhaustive list of all possible source error types?

This is a version of your code that actually compiles. When requesting help from people, I would encourage you to provide these examples yourself; there are many more people asking...

Can I use `context` for any error type that implements a trait without providing an exhaustive list of all possible source error types?

> I want to separate errors in such a way that I don't want to distinguish sources, so many different source errors are possible causes of my single domain error...

Can I use `context` for any error type that implements a trait without providing an exhaustive list of all possible source error types?

> it may be possible to do that by form `#[snafu(from(dyn std::error::Error, Box::new))]` I don't understand what this implementation would look like; would it be possible for you to provide...