MAYBE
919.19/297.02	MAYBE
919.19/297.02	
919.19/297.02	We are left with following problem, upon which TcT provides the
919.19/297.02	certificate MAYBE.
919.19/297.02	
919.19/297.02	Strict Trs:
919.19/297.02	  { app(l, nil()) -> l
919.19/297.02	  , app(nil(), k) -> k
919.19/297.02	  , app(cons(x, l), k) -> cons(x, app(l, k))
919.19/297.02	  , sum(app(l, cons(x, cons(y, k)))) ->
919.19/297.02	    sum(app(l, sum(cons(x, cons(y, k)))))
919.19/297.02	  , sum(cons(x, nil())) -> cons(x, nil())
919.19/297.02	  , sum(cons(x, cons(y, l))) -> sum(cons(plus(x, y), l))
919.19/297.02	  , plus(0(), y) -> y
919.19/297.02	  , plus(s(x), y) -> s(plus(x, y)) }
919.19/297.02	Obligation:
919.19/297.02	  runtime complexity
919.19/297.02	Answer:
919.19/297.02	  MAYBE
919.19/297.02	
919.19/297.02	None of the processors succeeded.
919.19/297.02	
919.19/297.02	Details of failed attempt(s):
919.19/297.02	-----------------------------
919.19/297.02	1) 'With Problem ... (timeout of 297 seconds)' failed due to the
919.19/297.02	   following reason:
919.19/297.02	   
919.19/297.02	   Computation stopped due to timeout after 297.0 seconds.
919.19/297.02	
919.19/297.02	2) 'Best' failed due to the following reason:
919.19/297.02	   
919.19/297.02	   None of the processors succeeded.
919.19/297.02	   
919.19/297.02	   Details of failed attempt(s):
919.19/297.02	   -----------------------------
919.19/297.02	   1) 'With Problem ... (timeout of 148 seconds) (timeout of 297
919.19/297.02	      seconds)' failed due to the following reason:
919.19/297.02	      
919.19/297.02	      Computation stopped due to timeout after 148.0 seconds.
919.19/297.02	   
919.19/297.02	   2) 'Fastest (timeout of 24 seconds) (timeout of 297 seconds)'
919.19/297.02	      failed due to the following reason:
919.19/297.02	      
919.19/297.02	      Computation stopped due to timeout after 24.0 seconds.
919.19/297.02	   
919.19/297.02	   3) 'Best' failed due to the following reason:
919.19/297.02	      
919.19/297.02	      None of the processors succeeded.
919.19/297.02	      
919.19/297.02	      Details of failed attempt(s):
919.19/297.02	      -----------------------------
919.19/297.02	      1) 'Polynomial Path Order (PS) (timeout of 297 seconds)' failed due
919.19/297.02	         to the following reason:
919.19/297.02	         
919.19/297.02	         The processor is inapplicable, reason:
919.19/297.02	           Processor only applicable for innermost runtime complexity analysis
919.19/297.02	      
919.19/297.02	      2) 'bsearch-popstar (timeout of 297 seconds)' failed due to the
919.19/297.02	         following reason:
919.19/297.02	         
919.19/297.02	         The processor is inapplicable, reason:
919.19/297.02	           Processor only applicable for innermost runtime complexity analysis
919.19/297.02	      
919.19/297.02	   
919.19/297.02	
919.19/297.02	3) 'Weak Dependency Pairs (timeout of 297 seconds)' failed due to
919.19/297.02	   the following reason:
919.19/297.02	   
919.19/297.02	   We add the following weak dependency pairs:
919.19/297.02	   
919.19/297.02	   Strict DPs:
919.19/297.02	     { app^#(l, nil()) -> c_1(l)
919.19/297.02	     , app^#(nil(), k) -> c_2(k)
919.19/297.02	     , app^#(cons(x, l), k) -> c_3(x, app^#(l, k))
919.19/297.02	     , sum^#(app(l, cons(x, cons(y, k)))) ->
919.19/297.02	       c_4(sum^#(app(l, sum(cons(x, cons(y, k))))))
919.19/297.02	     , sum^#(cons(x, nil())) -> c_5(x)
919.19/297.02	     , sum^#(cons(x, cons(y, l))) -> c_6(sum^#(cons(plus(x, y), l)))
919.19/297.02	     , plus^#(0(), y) -> c_7(y)
919.19/297.02	     , plus^#(s(x), y) -> c_8(plus^#(x, y)) }
919.19/297.02	   
919.19/297.02	   and mark the set of starting terms.
919.19/297.02	   
919.19/297.02	   We are left with following problem, upon which TcT provides the
919.19/297.02	   certificate MAYBE.
919.19/297.02	   
919.19/297.02	   Strict DPs:
919.19/297.02	     { app^#(l, nil()) -> c_1(l)
919.19/297.02	     , app^#(nil(), k) -> c_2(k)
919.19/297.02	     , app^#(cons(x, l), k) -> c_3(x, app^#(l, k))
919.19/297.02	     , sum^#(app(l, cons(x, cons(y, k)))) ->
919.19/297.02	       c_4(sum^#(app(l, sum(cons(x, cons(y, k))))))
919.19/297.02	     , sum^#(cons(x, nil())) -> c_5(x)
919.19/297.02	     , sum^#(cons(x, cons(y, l))) -> c_6(sum^#(cons(plus(x, y), l)))
919.19/297.02	     , plus^#(0(), y) -> c_7(y)
919.19/297.02	     , plus^#(s(x), y) -> c_8(plus^#(x, y)) }
919.19/297.02	   Strict Trs:
919.19/297.02	     { app(l, nil()) -> l
919.19/297.02	     , app(nil(), k) -> k
919.19/297.02	     , app(cons(x, l), k) -> cons(x, app(l, k))
919.19/297.02	     , sum(app(l, cons(x, cons(y, k)))) ->
919.19/297.02	       sum(app(l, sum(cons(x, cons(y, k)))))
919.19/297.02	     , sum(cons(x, nil())) -> cons(x, nil())
919.19/297.02	     , sum(cons(x, cons(y, l))) -> sum(cons(plus(x, y), l))
919.19/297.02	     , plus(0(), y) -> y
919.19/297.02	     , plus(s(x), y) -> s(plus(x, y)) }
919.19/297.02	   Obligation:
919.19/297.02	     runtime complexity
919.19/297.02	   Answer:
919.19/297.02	     MAYBE
919.19/297.02	   
919.19/297.02	   Empty strict component of the problem is NOT empty.
919.19/297.02	
919.19/297.02	
919.19/297.02	Arrrr..
919.60/297.46	EOF