MAYBE

We are left with following problem, upon which TcT provides the
certificate MAYBE.

Strict Trs:
  { eq(X, Y) -> false()
  , eq(n__0(), n__0()) -> true()
  , eq(n__s(X), n__s(Y)) -> eq(activate(X), activate(Y))
  , activate(X) -> X
  , activate(n__0()) -> 0()
  , activate(n__s(X)) -> s(X)
  , activate(n__inf(X)) -> inf(activate(X))
  , activate(n__take(X1, X2)) -> take(activate(X1), activate(X2))
  , activate(n__length(X)) -> length(activate(X))
  , inf(X) -> cons(X, n__inf(n__s(X)))
  , inf(X) -> n__inf(X)
  , take(X1, X2) -> n__take(X1, X2)
  , take(0(), X) -> nil()
  , take(s(X), cons(Y, L)) ->
    cons(activate(Y), n__take(activate(X), activate(L)))
  , 0() -> n__0()
  , s(X) -> n__s(X)
  , length(X) -> n__length(X)
  , length(cons(X, L)) -> s(n__length(activate(L)))
  , length(nil()) -> 0() }
Obligation:
  innermost runtime complexity
Answer:
  MAYBE

Arguments of following rules are not normal-forms:

{ take(0(), X) -> nil()
, take(s(X), cons(Y, L)) ->
  cons(activate(Y), n__take(activate(X), activate(L))) }

All above mentioned rules can be savely removed.

We are left with following problem, upon which TcT provides the
certificate MAYBE.

Strict Trs:
  { eq(X, Y) -> false()
  , eq(n__0(), n__0()) -> true()
  , eq(n__s(X), n__s(Y)) -> eq(activate(X), activate(Y))
  , activate(X) -> X
  , activate(n__0()) -> 0()
  , activate(n__s(X)) -> s(X)
  , activate(n__inf(X)) -> inf(activate(X))
  , activate(n__take(X1, X2)) -> take(activate(X1), activate(X2))
  , activate(n__length(X)) -> length(activate(X))
  , inf(X) -> cons(X, n__inf(n__s(X)))
  , inf(X) -> n__inf(X)
  , take(X1, X2) -> n__take(X1, X2)
  , 0() -> n__0()
  , s(X) -> n__s(X)
  , length(X) -> n__length(X)
  , length(cons(X, L)) -> s(n__length(activate(L)))
  , length(nil()) -> 0() }
Obligation:
  innermost runtime complexity
Answer:
  MAYBE

None of the processors succeeded.

Details of failed attempt(s):
-----------------------------
1) 'empty' failed due to the following reason:
   
   Empty strict component of the problem is NOT empty.

2) 'Best' failed due to the following reason:
   
   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) 'bsearch-popstar (timeout of 60 seconds)' failed due to the
            following reason:
            
            The input cannot be shown compatible
         
         2) 'Polynomial Path Order (PS) (timeout of 60 seconds)' failed due
            to the following reason:
            
            The input cannot be shown compatible
         
      
      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.
         
      
   


Arrrr..