tansy
tansy
All libraries in all mingw distributions I have (from 3.4 to date) use "\*nix" convention (\`.a', \`.dll.a'). Even rust guys recognise that: [Windows: Static libraries should end with .a not...
> because Visual Studio requires it in order to link to the DLL > doesn't it make sense to use the Windows naming convention for it? Yes, if this particular...
I get the point about (current) levels 10 - 12 (near_optimal). I will (still) investigate it further to check more details. I still stand by my opinion regarding levels 6...
> I'm not sure what you're referring to here, give that your patch would weaken levels 7-8, and not change levels 6 and 9 In simple words, yes. Like I...
It may be a problem with those compilers. I installed one for linux, from the same source, and it works. It also is on different machine but how do I...
Some option to ensure "traditional" sum format would be fine. If someone deliberately specifies it, they know what they are doing. I always give hash sum files descriptive extension do...
In my opinion there should be separate sum for xxh and xxh3. They are different hashes after all. For example: `xxhsum > file.xxh` `xxh3sum > file.xxh3`. The sums would be...
There is something I wanted to point out with xxhash. It popped into my head when I was reading about non/bsd hash result convention (#645) and about simple source code...
Thanks, it worked.
This level of complexity is unnecessary. All we need, in my opinion, is to split it into `xxh.h`, `xxh3.h`, and `xxhash.h`. With xxh.h for be xxh-hash, xxh3.h for xxh3-hash, xxhash.h...