2009
DOI: 10.1587/transinf.e92.d.235
|View full text |Cite
|
Sign up to set email alerts
|

Static Dependency Pair Method for Simply-Typed Term Rewriting and Related Techniques

Abstract: Keiichirou KUSAKARI†a) and Masahiko SAKAI †b) , Members SUMMARY A static dependency pair method, proposed by us, can effectively prove termination of simply-typed term rewriting systems (STRSs). The theoretical basis is given by the notion of strong computability. This method analyzes a static recursive structure based on definition dependency. By solving suitable constraints generated by the analysis result, we can prove the termination. Since this method is not applicable to every system, we proposed a class… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2

Citation Types

0
21
0

Year Published

2009
2009
2023
2023

Publication Types

Select...
4
1

Relationship

3
2

Authors

Journals

citations
Cited by 9 publications
(21 citation statements)
references
References 24 publications
0
21
0
Order By: Relevance
“…From this observation, we proposed notions of plain function-passing [16] and of safe function-passing [17], under which the static dependency pair method works well. In this section, we extend the notion of safe function-passing to RFPs, with the notions of a strong computability predicate and a safety function.…”
Section: Strong Computability Safety Function and Safe Function-passingmentioning
confidence: 99%
See 4 more Smart Citations
“…From this observation, we proposed notions of plain function-passing [16] and of safe function-passing [17], under which the static dependency pair method works well. In this section, we extend the notion of safe function-passing to RFPs, with the notions of a strong computability predicate and a safety function.…”
Section: Strong Computability Safety Function and Safe Function-passingmentioning
confidence: 99%
“…To formulate the notion of safe function-passing in a simple type setting, we introduced notions of peeling types and peeling orders [17]. We extend these notions to RFPs, and construct a strong computability predicate and a safety function.…”
Section: Constructing a Strong Computability Predicate And A Safety Fmentioning
confidence: 99%
See 3 more Smart Citations