Skip to content

Tree Edit Distance #25

Description

@VictorCMiraldo

We have already implemented tree edit distance; We already seen how a HDiff.Patch translated
to a GDiff.ES is worse, in terms of higher edit-script-cost, than a computed GDiff.ES.

Another thing we should do is count how many constructors we actually delete and insert
with a HDiff, and compare that with a gdiff. For that to be accurate, though, we must
not count the spine:

hdiffCost :: Patch -> Int
hdiffCost p = sum . holesGetHolesWith (uncurry' go) . holesLCP (cCtxDel (distr p)) (cCtxIns (distr p))
  where
    go p q = size p + size q

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions