sidju

(I realised how to handle my previous issue a minute after posting...)

Seemingly impossible right now, due to this not being supported by rust: https://github.com/rust-lang/rfcs/issues/1834 (To clarify, since it cannot be declared that X != Y the suggested impl overlaps with the...

Current workaround is to use `.map_msg` on the Node to covert it. The mapped function can further contain the Y to X implementation, saving a trait implementation if only called...

Upon further consideration I have suggestions for combinator names. map_ok and map_err have excellent clarity, they obviously map the ok/err case in the chain. To instead of implying mapping a...

The alternate solution would be to wait for async closures to hit stable, remove the option of combining with synchronous functions altogether (as people can just as well use an...

My current solution is to use PR #458. It adds a .map_async in addition to implementing Reply if both sides of Result implement reply. With that just implement reply on...

I wrote "probably" specifically because I haven't tested it, but I would expect a reduction in latencies and performance increase. Vec tends to perform better thanks to cache locality and...

For those looking into this in the future, here is my config: ``` [Unit] Description=btrbk daily backup Requires=network-online.target After=network-online.target RequiresMountsFor=/btrfs [Timer] OnCalendar=daily AccuracySec=10min Persistent=true [Install] WantedBy=timers.target ``` `network-online.target` means it...

In an attempt to rephrase this slightly more clearly (since I was confused and opposed until I understood): Functions would better return Result, so that: - Err can represent when...

I have already cut the trace connecting the VCC resistor to the RGB pin and that solved the issue for me. The pull-down resistor didn't cause any issues on the...