Various code simplification/fixes and a lot of typo/grammar fixes (may brake some stuff)
This commit is contained in:
@@ -7,7 +7,7 @@ import java.util.function.ToIntBiFunction;
|
||||
/**
|
||||
* Implementation of the <a href="https://en.wikipedia.org/wiki/Levenshtein_distance">Levenshtein distance algorithm</a>
|
||||
* that operate on characters. Its purpose is to compute a "distance" between two strings of characters, that represents
|
||||
* how many edition operations must be performed on the first string ({@code initialString}) to optain the second
|
||||
* how many edition operations must be performed on the first string ({@code initialString}) to obtain the second
|
||||
* one ({@code finalString}).
|
||||
* <p>
|
||||
* All the parameters of the algorithm are configurable:
|
||||
@@ -23,7 +23,7 @@ import java.util.function.ToIntBiFunction;
|
||||
* between the two strings.
|
||||
* <p>
|
||||
* A more advanced usage offer the possibility to progressively compute a distance from a predefined
|
||||
* {@code initialString} to a {@code finalString} that is feeded progressively using {@link #add(char)} or
|
||||
* {@code initialString} to a {@code finalString} that is fed progressively using {@link #add(char)} or
|
||||
* {@link #add(String)}. This is useful if the {@code finalString} is an input that is currently being typed by the
|
||||
* user, so the application can progressively update a list of suggested words based on the distance.
|
||||
* For this usage, you can use those constructors to avoid initializing the {@code finalString}:
|
||||
|
Reference in New Issue
Block a user