MAYBE We are left with following problem, upon which TcT provides the certificate MAYBE. Strict Trs: { purge(nil()) -> nil() , purge(.(x, y)) -> .(x, purge(remove(x, y))) , remove(x, nil()) -> nil() , remove(x, .(y, z)) -> if(=(x, y), remove(x, z), .(y, remove(x, z))) } Obligation: runtime complexity Answer: MAYBE None of the processors succeeded. Details of failed attempt(s): ----------------------------- 1) 'WithProblem (timeout of 60 seconds)' failed due to the following reason: Computation stopped due to timeout after 60.0 seconds. 2) 'Best' failed due to the following reason: None of the processors succeeded. Details of failed attempt(s): ----------------------------- 1) 'WithProblem (timeout of 30 seconds) (timeout of 60 seconds)' failed due to the following reason: Computation stopped due to timeout after 30.0 seconds. 2) 'Best' failed due to the following reason: None of the processors succeeded. Details of failed attempt(s): ----------------------------- 1) 'Polynomial Path Order (PS) (timeout of 60 seconds)' failed due to the following reason: The processor is inapplicable, reason: Processor only applicable for innermost runtime complexity analysis 2) 'bsearch-popstar (timeout of 60 seconds)' failed due to the following reason: The processor is inapplicable, reason: Processor only applicable for innermost runtime complexity analysis 3) 'Fastest (timeout of 5 seconds) (timeout of 60 seconds)' failed due to the following reason: None of the processors succeeded. Details of failed attempt(s): ----------------------------- 1) 'Bounds with minimal-enrichment and initial automaton 'match'' failed due to the following reason: match-boundness of the problem could not be verified. 2) 'Bounds with perSymbol-enrichment and initial automaton 'match'' failed due to the following reason: match-boundness of the problem could not be verified. 3) 'Innermost Weak Dependency Pairs (timeout of 60 seconds)' failed due to the following reason: We add the following weak dependency pairs: Strict DPs: { purge^#(nil()) -> c_1() , purge^#(.(x, y)) -> c_2(x, purge^#(remove(x, y))) , remove^#(x, nil()) -> c_3() , remove^#(x, .(y, z)) -> c_4(x, y, remove^#(x, z), y, remove^#(x, z)) } and mark the set of starting terms. We are left with following problem, upon which TcT provides the certificate MAYBE. Strict DPs: { purge^#(nil()) -> c_1() , purge^#(.(x, y)) -> c_2(x, purge^#(remove(x, y))) , remove^#(x, nil()) -> c_3() , remove^#(x, .(y, z)) -> c_4(x, y, remove^#(x, z), y, remove^#(x, z)) } Strict Trs: { purge(nil()) -> nil() , purge(.(x, y)) -> .(x, purge(remove(x, y))) , remove(x, nil()) -> nil() , remove(x, .(y, z)) -> if(=(x, y), remove(x, z), .(y, remove(x, z))) } Obligation: runtime complexity Answer: MAYBE We estimate the number of application of {1,3} by applications of Pre({1,3}) = {2,4}. Here rules are labeled as follows: DPs: { 1: purge^#(nil()) -> c_1() , 2: purge^#(.(x, y)) -> c_2(x, purge^#(remove(x, y))) , 3: remove^#(x, nil()) -> c_3() , 4: remove^#(x, .(y, z)) -> c_4(x, y, remove^#(x, z), y, remove^#(x, z)) } We are left with following problem, upon which TcT provides the certificate MAYBE. Strict DPs: { purge^#(.(x, y)) -> c_2(x, purge^#(remove(x, y))) , remove^#(x, .(y, z)) -> c_4(x, y, remove^#(x, z), y, remove^#(x, z)) } Strict Trs: { purge(nil()) -> nil() , purge(.(x, y)) -> .(x, purge(remove(x, y))) , remove(x, nil()) -> nil() , remove(x, .(y, z)) -> if(=(x, y), remove(x, z), .(y, remove(x, z))) } Weak DPs: { purge^#(nil()) -> c_1() , remove^#(x, nil()) -> c_3() } Obligation: runtime complexity Answer: MAYBE Empty strict component of the problem is NOT empty. Arrrr..