Markus Triska

`length_rundown` and `length_addendum` are predicates internal in `library(lists)`, whereas `length` is an exported predicate. At the time the completion is tried, none of these predicates are even available, and the...

Maybe it could be worth considering to take **`current_predicate/1`** into account for possible completions. For instance, we have: $ scryer-prolog -f ?- current_predicate(P). P = term_expansion/2 ; P = verify_attributes/3...

> this is likely due to short atoms no longer being stored in the atom table Yes indeed, this seems to be the reason! Atoms up to length 6 (in...

I would like to second this, specifically also because commit hashes occur in **commit messages**. As an example, git commit 05ba5f43589efb3e02526ebb7719587b3e4bba77 refers to commit 4fd37335f576240c25dfbfe6e70441aff166c60e in its description, and force-pushing...

That being said, you can force the local branch to the latest head of rebis-dev with: $ git reset --hard origin/rebis-dev

> I prefer rebasing and keeping the history in a state that is easy to understand and inspect Yes, I second that as well!

Related: https://github.com/mthom/scryer-prolog/issues/438

Please note that the top level is out of scope of the standard: 3.185 top level: A process whereby a Prolog processor repeatedly inputs and executes * queries. NOTE -...

I think there is an example in https://github.com/mthom/scryer-prolog/tree/master/src/machine/lib_machine, does it help?

Currently, it is only a single file. Conceptually, we can distinguish at least the following parts, occurring roughly in this order in the source file: - **domain operations**, an essential...