UWN

`length(_,_)` uses memory for the list. So it is not a good example to draw conclusions from.

This here works: ``` b(A,B,C):-between(A,B,C),false. b(_,_,_). qo :- b(1,100000000,_). ?- qo. true.

It would help here to issue a clean resource error. In this manner one could distinguish between copystack/global heap overflows and call stack/local stack overflows.

Shorter: ``` :- use_module(library(clpz)). arc(rome, paris). arc(paris, palaiseau). crash :- X = paris, (arc(X, Z) ; arc(Z, X)), Interest #= Interest_tempo + 1, false, Z=Interest_tempo. :- initialization(crash). ulrich@gupu:~/scryer$ /opt/gupu/scryer-prolog/target/release/scryer-prolog -f...

@mhemery: Is this closable for you?

More or less, built-in calls need to be added, probably. A property, that I would love to be observed exactly is that [failure-slices](https://stackoverflow.com/tags/failure-slice) do indeed have less or equal as...

There is already `call_with_inference_limit/3`, so it should not be that difficult.

The question is really when this is needed. At runtime or at compile time? One solution for compile time might be to change the non-monotonic mode to SICStus-style mode. SICStus...

Or to put it the other way round: monotonic programs do run also with that flag disabled. And those who use it in that looser mode still get the benefit...

The motivation behind `/` is that it is a projection of the real division onto the integers.