Sedat Kapanoğlu
Sedat Kapanoğlu
Another interested party here. Would this work with AB and BB versions?
Is there any reason to keep .NET 3.5 compatibility for future versions? (.NET 3.5 clients can keep using older versions anyway?)
What's the minimum .NET version that needs to be supported?
`BigInteger` needs `net35` target to be dropped from the project. However, since that's a breaking change, I'm not sure how versioning should follow. (2.0? or just go with the regular...
Also, there is a workaround: you can remove the contents of PackageReference tag to Bricelam.Xxx (IncludeAssets etc), then it works with other assemblies too.
This code directly throws NullReferenceException on me with the latest version (4.0.3) of the library on NuGet: ```csharp public class LoginModel : PageModel { private readonly IConfiguration config; public LoginModel(IConfiguration...
That's a great suggestion. I'll add it to the pipeline.
Thanks @george-polevoy, yes I've tried BenchmarkDotNet before, but it takes too long to come up with results. I agree that these benchmarks aren't as accurate though. I'm relying on benchmarks...
Good question. I don't have tests for endianness and definitely haven't written the code with endianness in mind. I only tested it on little endian. Let me check this out.
I checked this out (finally), SipHash and MurmurHash seem to be endianness sensitive. Fnv1 and Fnv1a should be okay. Changes needed to make them endian-aware.