MAYBE
754.16/297.10	MAYBE
754.16/297.10	
754.16/297.10	We are left with following problem, upon which TcT provides the
754.16/297.10	certificate MAYBE.
754.16/297.10	
754.16/297.10	Strict Trs:
754.16/297.10	  { intlist(nil()) -> nil()
754.16/297.10	  , intlist(cons(x, y)) -> cons(s(x), intlist(y))
754.16/297.10	  , intlist(cons(x, nil())) -> cons(s(x), nil())
754.16/297.10	  , int(x, x) -> cons(x, nil())
754.16/297.10	  , int(s(x), s(y)) -> intlist(int(x, y))
754.16/297.10	  , int(s(x), 0()) -> nil()
754.16/297.10	  , int(0(), s(y)) -> cons(0(), int(s(0()), s(y))) }
754.16/297.10	Obligation:
754.16/297.10	  derivational complexity
754.16/297.10	Answer:
754.16/297.10	  MAYBE
754.16/297.10	
754.16/297.10	None of the processors succeeded.
754.16/297.10	
754.16/297.10	Details of failed attempt(s):
754.16/297.10	-----------------------------
754.16/297.10	1) 'Inspecting Problem... (timeout of 297 seconds)' failed due to
754.16/297.10	   the following reason:
754.16/297.10	   
754.16/297.10	   Computation stopped due to timeout after 297.0 seconds.
754.16/297.10	
754.16/297.10	2) 'Fastest (timeout of 60 seconds)' failed due to the following
754.16/297.10	   reason:
754.16/297.10	   
754.16/297.10	   Computation stopped due to timeout after 60.0 seconds.
754.16/297.10	
754.16/297.10	3) 'iteProgress (timeout of 297 seconds)' failed due to the
754.16/297.10	   following reason:
754.16/297.10	   
754.16/297.10	   Fail
754.16/297.10	
754.16/297.10	4) 'bsearch-matrix (timeout of 297 seconds)' failed due to the
754.16/297.10	   following reason:
754.16/297.10	   
754.16/297.10	   The input cannot be shown compatible
754.16/297.10	
754.16/297.10	
754.16/297.10	Arrrr..
754.16/297.13	EOF