Analyzes completeness of syntactic anti-unification in software, suggesting improvements in code transformation.
In syntactic anti-unification, one is concerned with finding the commonalities between terms, while (uniformly) abstracting their differences.The original goal of anti-unification development in the seventies was to automate inductive reasoning.Recent applications of anti-unification techniques include efficiently transforming sequential code into parallel code, detecting code clones, and preventing software failures.Previous work addressed the elements required to verify, in the Prototype Verification System (PVS), termination and soundness of a functional algorithm based on inference rules for syntactic anti-unification.This paper dissects all aspects required to formally establish the completeness of the rule-based algorithm, highlighting the significant differences in the formalizations of anti-unification and unification.
No takes yet. Share an insight, caveat, or question.
Ayala-Rincón et al. (2026) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: