commits
As far as I can tell, `argh` doesn't support multicall binaries, I could
try to hack my own support, or we can swit to clap.
The size difference isn't too much:
| build | size (release) |
|-----------------------------------|---------------:|
| `argh` | `513KB` |
| `clap` (default-features = false) | `628KB` |
| `clap` (default-features = true) | `731KB` |
It produces a smaller binary (513KB vs 522KB), and it is better tested.
From what I've heard from embedded developers, the `z` opt-level can
have miscompilations.
Why would you have a non UTF-8 path? Idk, but this simplifies the code
and reduces the error conditions so...
I don't have .direnv in my global .gitignore (I probably should), but
since this project has an .envrc, it should ignore the direnv cache.
this should better support non-UNIX and be less error-prone in general
- `PathBuf` more correctly represents what this field is
- this is needed for the next commit
fingers crossed this works as i hope
i wasn't sure what i was going to call it so i called it "nvd" lol
fixes https://github.com/isabelroses/lix-diff/issues/1
As far as I can tell, `argh` doesn't support multicall binaries, I could
try to hack my own support, or we can swit to clap.
The size difference isn't too much:
| build | size (release) |
|-----------------------------------|---------------:|
| `argh` | `513KB` |
| `clap` (default-features = false) | `628KB` |
| `clap` (default-features = true) | `731KB` |