Usage in .NetStandard2.0 library can cause MethodNotFound exception about quickenshtein HOT 3 CLOSED

Oh, that's interesting - never realised that! I think my original intention with the string variant was to add some minor optimizations for .NET Framework which seemed irrelevant for .NET Core with ReadOnlySpan<char> etc. Its definitely a good idea to re-evaluate whether that is truly useful and whether I don't just do as you've suggested and call the overload.

from quickenshtein.

Again, great catch for finding this issue, raising it and submitting a PR - I really appreciate it! Will release a new version with this change now!

from quickenshtein.

Hey @Turnerj, same thing here is happening but for netstandard2.1. In my case, I am calling public unsafe static int GetDistance(ReadOnlySpan<char> source, ReadOnlySpan<char> target, CalculationOptions calculationOptions) directly. There's no issue if I call Levenshtein.GetDistance(string, string) instead.

from quickenshtein.