I don't know the root cause of the issue mentioned in https://github.com/aarondandy/WeCantSpell.Hunspell/issues/78 but I have a hunch this might be related. I'm hopeful that moving away from Environment.TickCount will at least make the code a bit more resilient. This change comes with some reduced performance when checking incorrect words, but I think it is worth the cost. Based on what I have read, Environment.TickCount isn't very reliable, especially after 25 days . I hope DateTime.Utc.Ticks can be more reliable.
I don't know the root cause of the issue mentioned in https://github.com/aarondandy/WeCantSpell.Hunspell/issues/78 but I have a hunch this might be related. I'm hopeful that moving away from
Environment.TickCountwill at least make the code a bit more resilient. This change comes with some reduced performance when checking incorrect words, but I think it is worth the cost. Based on what I have read,Environment.TickCountisn't very reliable, especially after 25 days . I hopeDateTime.Utc.Tickscan be more reliable.