interpretations
MAYBE
We are left with following problem, upon which TcT provides the
certificate MAYBE.
Strict Trs:
{ r(xs, ys, zs, nil()) -> xs
, r(xs, nil(), zs, cons(w, ws)) ->
r(xs, xs, cons(succ(zero()), zs), ws)
, r(xs, cons(y, ys), nil(), cons(w, ws)) ->
r(xs, xs, cons(succ(zero()), nil()), ws)
, r(xs, cons(y, ys), cons(z, zs), cons(w, ws)) ->
r(ys, cons(y, ys), zs, cons(succ(zero()), cons(w, ws))) }
Obligation:
innermost runtime complexity
Answer:
MAYBE
None of the processors succeeded.
Details of failed attempt(s):
-----------------------------
1) 'matrix interpretation of dimension 3' failed due to the
following reason:
The input cannot be shown compatible
2) 'matrix interpretation of dimension 1' failed due to the
following reason:
The input cannot be shown compatible
3) 'custom shape polynomial interpretation' failed due to the
following reason:
The input cannot be shown compatible
4) 'custom shape polynomial interpretation' failed due to the
following reason:
The input cannot be shown compatible
Arrrr..
lmpo
MAYBE
We are left with following problem, upon which TcT provides the
certificate MAYBE.
Strict Trs:
{ r(xs, ys, zs, nil()) -> xs
, r(xs, nil(), zs, cons(w, ws)) ->
r(xs, xs, cons(succ(zero()), zs), ws)
, r(xs, cons(y, ys), nil(), cons(w, ws)) ->
r(xs, xs, cons(succ(zero()), nil()), ws)
, r(xs, cons(y, ys), cons(z, zs), cons(w, ws)) ->
r(ys, cons(y, ys), zs, cons(succ(zero()), cons(w, ws))) }
Obligation:
innermost runtime complexity
Answer:
MAYBE
The input cannot be shown compatible
Arrrr..
mpo
MAYBE
We are left with following problem, upon which TcT provides the
certificate MAYBE.
Strict Trs:
{ r(xs, ys, zs, nil()) -> xs
, r(xs, nil(), zs, cons(w, ws)) ->
r(xs, xs, cons(succ(zero()), zs), ws)
, r(xs, cons(y, ys), nil(), cons(w, ws)) ->
r(xs, xs, cons(succ(zero()), nil()), ws)
, r(xs, cons(y, ys), cons(z, zs), cons(w, ws)) ->
r(ys, cons(y, ys), zs, cons(succ(zero()), cons(w, ws))) }
Obligation:
innermost runtime complexity
Answer:
MAYBE
The input cannot be shown compatible
Arrrr..
popstar
MAYBE
We are left with following problem, upon which TcT provides the
certificate MAYBE.
Strict Trs:
{ r(xs, ys, zs, nil()) -> xs
, r(xs, nil(), zs, cons(w, ws)) ->
r(xs, xs, cons(succ(zero()), zs), ws)
, r(xs, cons(y, ys), nil(), cons(w, ws)) ->
r(xs, xs, cons(succ(zero()), nil()), ws)
, r(xs, cons(y, ys), cons(z, zs), cons(w, ws)) ->
r(ys, cons(y, ys), zs, cons(succ(zero()), cons(w, ws))) }
Obligation:
innermost runtime complexity
Answer:
MAYBE
The input cannot be shown compatible
Arrrr..
popstar-ps
MAYBE
We are left with following problem, upon which TcT provides the
certificate MAYBE.
Strict Trs:
{ r(xs, ys, zs, nil()) -> xs
, r(xs, nil(), zs, cons(w, ws)) ->
r(xs, xs, cons(succ(zero()), zs), ws)
, r(xs, cons(y, ys), nil(), cons(w, ws)) ->
r(xs, xs, cons(succ(zero()), nil()), ws)
, r(xs, cons(y, ys), cons(z, zs), cons(w, ws)) ->
r(ys, cons(y, ys), zs, cons(succ(zero()), cons(w, ws))) }
Obligation:
innermost runtime complexity
Answer:
MAYBE
The input cannot be shown compatible
Arrrr..