Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why switch around insertion and deletion costs? #15

Open
robertfeldt opened this issue Apr 14, 2018 · 0 comments
Open

Why switch around insertion and deletion costs? #15

robertfeldt opened this issue Apr 14, 2018 · 0 comments

Comments

@robertfeldt
Copy link

robertfeldt commented Apr 14, 2018

Is there some specific reason for switching around the insertion and deletion costs like this:

function levenshtein(source::AbstractString, target::AbstractString, deletion_cost::R, insertion_cost::S, substitution_cost::T) where {R<:Real,S<:Real,T<:Real}
    return levenshtein!(target, source, insertion_cost, deletion_cost, substitution_cost)
end

I find it mildly confusing when reading the source.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant