We need a better typo library
mattmoor opened this issue · 0 comments
mattmoor commented
I got this from Go report, but it catches none of my intentional typos.
I'm not really concerned with runtime efficiency, so something using levenshtein distance seems fine.
cc @jonjohnson