Kauê Hunnicutt Bazilli

> Like `length(L,L)`. Here, it is evident that this computation will take infinitely long. I don't understand why this is the case. I think the obvious thing to do here...

I can't reproduce. At least not with such a high value. ``` .../repos/dev/scryer-prolog> ./target/release/scryer-prolog -f heap_memory_limit ?- [user]. get_heap_limit(Lim) :- '$get_heap_limit'(Lim). set_heap_limit(Lim) :- '$set_heap_limit'(Lim). ?- set_heap_limit(100000). true. ?- set_heap_limit(10000). true....

Ok, I can reproduce without the `-f` option. It seems loading modules is causing some weird things here.

It seems to be a problem with backtracking. I think it's doing the backtracking even though there is no frame from where it could load, so I think it hits...

Wow, I was just working on something similar as a stepping stone to dealing with actual out of memory errors in the heap (#16). Currently the heap is just a...

> There must be a way to do this in rust when even ps and top know this We could just do what they do, which is reading `/proc//stat` (we...

> Who writes this message memory allocation of 67108864 bytes failed? It seems this is rust. It's the Rust global allocator. It doesn't give a fallible interface, it just shows...

Would it also be good to have this limit by default, and maybe dynamic? Maybe we could check how much memory is available in the system once in a while...

For reference, the residual is the same with both permutations in this case: ```prolog ?- L = [1|L], dif(L, B). L = [1|L], dif:dif([1|1],B). % Unexpected ?- dif(L, B), L...

I think, following the pattern of how Scryer does things like the toplevel, that the thing we should do here is the one that is more close to actual Prolog...