Odd behavior on backtracking about trealla HOT 2 OPEN

On Sat, Oct 1, 2022 at 12:32 AM guregu ***@***.***> wrote: Reduced it further: :- module(js_toplevel, [js_ask/1]). :- use_module(library(lists)). js_ask(Input) :- read_term_from_chars(Query, [variable_names(Vars)], Input), query(Query, Status), write(Vars), nl, write(Status), nl, call_any_predicate(Status). % deleting this fixes it? call_any_predicate(_). write_result(Status, Solution) :- write(Status), write(' '), write(Solution), nl. query(Query, Status) :- % weird: catch(Query, Error, true), % ok: % call(Query), query_status(true, Error, Status). query_status(_OK, Error, error) :- nonvar(Error), !.query_status(true, _, success).query_status(false, _, failure). person(socrates).person(plato).mortal(X) :- person(X). I think optimization is the culprit: $ ./tpl --version Trealla Prolog (c) Infradig 2020-2022, v2.2.15 # weird $ ./tpl js_toplevel.pl -g 'js_ask("mortal(X)")' --ns [X=socrates] success true; # ok $ ./tpl js_toplevel.pl -O0 -g 'js_ask("mortal(X)")' --ns [X=socrates] success true; [X=plato] success true; — Reply to this email directly, view it on GitHub <#52 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFNKSESLJQEYI2KQFZKFFILWA32ZHANCNFSM6AAAAAAQZZVIGA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>