We consider the system h14. Alphabet: 0 : [] --> nat cons : [] --> nat -> natlist -> natlist foldl : [] --> (nat -> nat -> nat) -> nat -> natlist -> nat nil : [] --> natlist plus : [] --> nat -> nat -> nat sum : [] --> natlist -> nat Rules: foldl (/\x./\y.f x y) z nil => z foldl (/\x./\y.f x y) z (cons u v) => foldl (/\w./\x'.f w x') (f z u) v sum x => foldl (/\y./\z.plus y z) 0 x Using the transformations described in [Kop11], this system can be brought in a form without leading free variables in the left-hand side, and where the left-hand side of a variable is always a functional term or application headed by a functional term. We now transform the resulting AFS into an AFSM by replacing all free variables by meta-variables (with arity 0). This leads to the following AFSM: Alphabet: 0 : [] --> nat cons : [nat * natlist] --> natlist foldl : [nat -> nat -> nat * nat * natlist] --> nat nil : [] --> natlist plus : [] --> nat -> nat -> nat sum : [natlist] --> nat ~AP1 : [nat -> nat -> nat * nat] --> nat -> nat Rules: foldl(/\x./\y.~AP1(F, x) y, X, nil) => X foldl(/\x./\y.~AP1(F, x) y, X, cons(Y, Z)) => foldl(/\z./\u.~AP1(F, z) u, ~AP1(F, X) Y, Z) sum(X) => foldl(/\x./\y.~AP1(plus, x) y, 0, X) ~AP1(F, X) => F X Symbol ~AP1 is an encoding for application that is only used in innocuous ways. We can simplify the program (without losing non-termination) by removing it. This gives: Alphabet: 0 : [] --> nat cons : [nat * natlist] --> natlist foldl : [nat -> nat -> nat * nat * natlist] --> nat nil : [] --> natlist plus : [nat * nat] --> nat sum : [natlist] --> nat Rules: foldl(/\x./\y.X(x, y), Y, nil) => Y foldl(/\x./\y.X(x, y), Y, cons(Z, U)) => foldl(/\z./\u.X(z, u), X(Y, Z), U) sum(X) => foldl(/\x./\y.plus(x, y), 0, X) We use the dependency pair framework as described in [Kop12, Ch. 6/7], with static dependency pairs (see [KusIsoSakBla09] and the adaptation for AFSMs and accessible arguments in [FuhKop19]). We thus obtain the following dependency pair problem (P_0, R_0, computable, formative): Dependency Pairs P_0: 0] foldl#(/\x./\y.X(x, y), Y, cons(Z, U)) =#> foldl#(/\z./\u.X(z, u), X(Y, Z), U) 1] sum#(X) =#> foldl#(/\x./\y.plus(x, y), 0, X) Rules R_0: foldl(/\x./\y.X(x, y), Y, nil) => Y foldl(/\x./\y.X(x, y), Y, cons(Z, U)) => foldl(/\z./\u.X(z, u), X(Y, Z), U) sum(X) => foldl(/\x./\y.plus(x, y), 0, X) Thus, the original system is terminating if (P_0, R_0, computable, formative) is finite. We consider the dependency pair problem (P_0, R_0, computable, formative). We place the elements of P in a dependency graph approximation G (see e.g. [Kop12, Thm. 7.27, 7.29], as follows: * 0 : 0 * 1 : 0 This graph has the following strongly connected components: P_1: foldl#(/\x./\y.X(x, y), Y, cons(Z, U)) =#> foldl#(/\z./\u.X(z, u), X(Y, Z), U) By [Kop12, Thm. 7.31], we may replace any dependency pair problem (P_0, R_0, m, f) by (P_1, R_0, m, f). Thus, the original system is terminating if (P_1, R_0, computable, formative) is finite. We consider the dependency pair problem (P_1, R_0, computable, formative). We apply the subterm criterion with the following projection function: nu(foldl#) = 3 Thus, we can orient the dependency pairs as follows: nu(foldl#(/\x./\y.X(x, y), Y, cons(Z, U))) = cons(Z, U) |> U = nu(foldl#(/\z./\u.X(z, u), X(Y, Z), U)) By [FuhKop19, Thm. 61], we may replace a dependency pair problem (P_1, R_0, computable, f) by ({}, R_0, computable, f). By the empty set processor [Kop12, Thm. 7.15] this problem may be immediately removed. As all dependency pair problems were succesfully simplified with sound (and complete) processors until nothing remained, we conclude termination. +++ Citations +++ [FuhKop19] C. Fuhs, and C. Kop. A static higher-order dependency pair framework. In Proceedings of ESOP 2019, 2019. [Kop11] C. Kop. Simplifying Algebraic Functional Systems. In Proceedings of CAI 2011, volume 6742 of LNCS. 201--215, Springer, 2011. [Kop12] C. Kop. Higher Order Termination. PhD Thesis, 2012. [KusIsoSakBla09] K. Kusakari, Y. Isogai, M. Sakai, and F. Blanqui. Static Dependency Pair Method Based On Strong Computability for Higher-Order Rewrite Systems. In volume 92(10) of IEICE Transactions on Information and Systems. 2007--2015, 2009.