search for: typocorrectionconsumer

...returns an edit distance of 2. One of the other tests (Parser/objc-quirks.m) is actually a crash. + // maxDistance (aka D) directly influences the width of the strip (2*D+1) + // we arbitrarily restrict it in case the caller did not see fit to do it + // (from clang\lib\Sema\SemaLookup.cpp in TypoCorrectionConsumer::FoundName) + unsigned const maxDistance = std::min(unsigned((otherLength+2)/3), + maxEditDistance); I don't think this belongs here. We can count on the client to supply a reasonable maxEditDistance. If our performance is going to degrade horribly when...

Hello Doug, *putting llvmdev in copy since they are concerned too* I've finally got around to finish a working implementation of the typical Levenshtein Distance with the diagonal optimization. I've tested it against the original llvm implementation and checked it on a set of ~18k by randomly generating a variation of each word and checking that both implementations would return the