|
|
|
|
|
|
by lmm
30 days ago
|
|
|
> And maybe calculate the Levenshtein distance between all terms if it’s not found, and just assume it’s the closest one. So when a library adds a new method, it silently changes which method client code calls? That's a bit too magic IMO. I think the best you can do is be case-insensitive and ban methods that differ only in case (or, if you want to extend the idea a bit more radically, ban having things in the namespace within Levenshtein distance x of each other, and then you can autocorrect errors smaller than x/2). |
|
|