david-bakin
(Just started using `dirhash` when making backups of lots of VHDs, their split archives, their par2 files, etc. and it is invaluable at catching occasional errors writing to external USB drives ... thank you! I _like_ the flexibility - both hash and verify, choice of hash algorithm, etc.) I'd like to be able to specify multiple hash algorithms, e.g., both BLAKE3 and SHA256. Because it may happen that when I'm comparing hash values against that provided by some source, in some cases they may specify SHA256 or MD5 or something, while for my own purposes (validating backups to external USB drives) I prefer to use something else - e.g., BLAKE3 - consistently. If implemented as a feature I'd also suggest writing the hash values to the output file in the order specified on the command line. Reason this might be nice is that the bottleneck is most often device input speeds - especially when talking to external drives (even at USB 3.0 speeds). CPU load is pretty minimal - at least when using `-mscrypto`: I can run multiple `dirhash`es on different (SSD but not NVMe) drives with them maxing out on read speed while my CPU load is below 30%, on a 4yr old 4core laptop. So it would be nice to be able to read a terabyte or so off the drive only _once_ even though getting multiple hashes computed.