samuel-lucas6 / milva Goto Github PK

Windows 7, Milva 1.1.0, b3sum 0.3.7, hashsum 1.0

$ milva.exe --blake3 milva.exe
milva.exe: af1349b9f5f9a1a6a0404dea36dcc9499bcb25c9adc112b7cc9a93cae41f3262

$ b3sum.exe milva.exe
21bc827a71ac67d907aa51e0ae4d3f26e3448a40c5aaed5df298cc75d1cdd55a  milva.exe

$ hashsum_win64.exe -v -t b3 milva.exe                 
21bc827a71ac67d907aa51e0ae4d3f26e3448a40c5aaed5df298cc75d1cdd55a milva.exe 

Does it make sense to add the functionality to hash text?

I think it can be added fairly easily by adding a t/text bool flag (with false as the default) and passing it to the HashEachFile method and changing the GetHash method to accept a Stream instead of a FileStream and then in the HashEachFile method if the Text flag is true in the forEach loop we can convert the text to a Stream.

If you think it makes sense I can work on it.

Version:
Milva v1.4.0

OS: Windows 10 21H2

test1.xyz size: 2,00 GB (2.147.483.648 bytes)

Error:

milva --blake3 test1.xyz
test1.xyz - Error: System.IO.IOException