Sivizius

I am new to restic and ran into the same problem. Because my first backup of everything failed, I tried to backup directory by directory. But then I tried to...

Could it be a good idea to add another command-line flag `--chain `, which always uses the last snapshot in this branch as parent and if you have multiple host,...

On modern systems, e.g. amd64 with SSE ```rust let x = [0u8; 16]; let y = [1u8; 16]; let z = x ^ y; ``` could be optimised as a...

I do not understand the test failure or how this is related to my and your changes. Is there something I could do to finish this PR?

I guess the issue is: ```rust use foo::module; use foo::module as mydyl; ``` should be merged as: ```rust use foo::module::{self, self as mydyl}; ``` But functions should be merged differently:...

```rust use { super::harriblex, super::harriblex::{ Iraquant, Mediviction }, }; ``` should be merged to: ```rust use super::harriblex::{self, Iraquant, Mediviction}; ``` and not: ```rust use super::{ harriblex, harriblex::{Iraquant, Mediviction}, }; ```...

I rebased it, is there anything else left to do?

I suggest to add a `--colour=` option, that defaults to `auto` which is the status quo. With `never`, `shouldANSI` must always return `false`, while with `always`, it must always return...

Sorry for the late answer, I somehow forgot, I opened this PR m). > it's a bit hard to audit simply because Rust macros are hard to read. Well, either...

I refactored the `allow!`-macro and added some documentation/comments. However, The issue of a second crate remains.