Anatoly Zhmur
Company: Broadridge
In 2002, with the release of .NET, we got a fairly primitive version of the hash function for strings. In 2010, it was updated, and the current version has gone even further.
Let's talk about the history of hash functions in .NET, why this is the case, and what requirements apply to them.
We'll also touch on the topic of cryptographic functions to understand why they're needed at all and why they're not used by default.
Let's look at how the quality of hash functions is checked in the SMHasher package.
The benchmark will be XXH3 and its .NET implementation, which overtakes the current string.gethashcode
in speed and is likely superior in quality.
Company: Broadridge
Company: EPAM