dpc
I think this might have been an user error as well. My apologies.
> The current implementation was easy to get up and running without making it too hard to juggle all the artifacts Yes. :) I was thinking this will be particularly...
Do you have any link at hand where I could read about what is actually going on here? It seems like Nix does some scanning of binaries to find dependencies...
This is a must.
It's not clear to me how to "organize" my errors. One big error? Many? I've seen somewhere on reddit that I'm supposed to define new `Error` in each module or...
Hmm... For some errors I'd like to ignore the `source` altogether, because I don't want to tie the error type with the type of underlying issue.... hmmmm... I can't do...
(just to be clearn - I'm not neccesarily looking for anwsers, just describing my thought process) Is there any way to turn an error into snafu-error automatically / programmaticaly (`Into`)...
Maybe https://docs.rs/snafu/0.4.1/snafu/trait.IntoError.html ? Hard to tell.
I've decided to start morning with reading any existing discussion from reddit/Rust fora about `snafu`. Turned out, I've been looking exactly for the pattern described here: https://www.reddit.com/r/rust/comments/bgy80y/any_experiences_with_snafu/elp5m3g/
I got at least enough understanding to help myself with: ``` trait ResultExt { type T; fn erased(self) -> std::result::Result std::result::Result