gchristensen changed the topic of #nixos-borg to: https://www.patreon.com/ofborg https://monitoring.nix.ci/dashboard/db/ofborg?refresh=10s&orgId=1&from=now-1h&to=now "I get to skip reviewing the PHP code and just wait until it is rewritten in something sane, like POSIX shell. || https://logs.nix.samueldr.com/nixos-borg
orivej has quit [Ping timeout: 250 seconds]
orivej has joined #nixos-borg
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-borg
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-borg
<Mic92> I prefer adding context to my errors so users know what went wrong: https://github.com/Mic92/cntr/blob/master/src/exec.rs#L46
<Mic92> does error_chain the same?
<gchristensen> nice
<gchristensen> not sure
<gchristensen> failure can add backtraces and context I think
<Mic92> This is what also liked about go projects that not just bubble up libc errnos to to user. The only disadvantage there is, that it is not possible to hide the control flow boilercode behind macros.
<gchristensen> :)
<gchristensen> when I was working in Go, Idid hide it behind macros
<gchristensen> I programmed my keyboard to have macro keys for ", err = " and "if err != nil"
<gchristensen> :P
<Mic92> this is probably not the right abstraction for libraries though, where you want to differentiate error types more: https://github.com/Mic92/cntr/blob/master/src/types.rs#L21
<gchristensen> right, I tihnk I want more enum action
c0bw3b_ has joined #nixos-borg
orivej has quit [Ping timeout: 244 seconds]
orivej has joined #nixos-borg
c0bw3b_ has quit [Remote host closed the connection]