scryer-prolog VS AoC

thank you! the scryer community deserves much of the credit too. everyone is welcome and encouraged to join us at https://github.com/mthom/scryer-prolog! some exciting plans in the pipe

Djot is the markup syntax that is used for the documentation of Scryer Prolog, using a parser written in Prolog:

https://github.com/aarroyoc/djota

It works well so far. One of the few limitations I noticed so far pertains to the formatting of tables. For instance, consider the table used in library(format) to describe control sequences:

https://github.com/mthom/scryer-prolog/blob/b0566e41503a6c8d...

It contains several entries that span multiple lines, yet are meant to denote only a single row of the table, such as:

    % | `~Nr`    |  where N is an integer between 2 and 36: format the            |

There's a nice book[1][2] about Prolog, with modern characteristics. Moreover, there are things like ProbLog[3] and DeepProbLog[4] that allow you to use probabilistic reasoning and power of machine learning. I am personally looking forward for Scryer Prolog[5] to achieve its goals.

[1] https://www.metalevel.at/prolog

[2] https://github.com/triska/the-power-of-prolog

[3] https://github.com/ML-KULeuven/problog

[4] https://github.com/ML-KULeuven/deepproblog

[5] https://github.com/mthom/scryer-prolog

One use case would be for example Scryer-prolog. The latter is a very fast and easy to use Prolog. It includes high performance constraint solving (e.g. CLP(ℤ)). I'd write a bridge to this prolog, but not if it is too cumbersome.

if native Prolog, which one? scryer-prolog seems to be constantly mentioned a having fast string support and useful libraries for dealing with JSON and web APIs

No, what I'm describing is the "monadic" behaviour of `phrase_from_file/2` and similar predicates. In conjunction with definite clause grammars, this means that your I/O operations either conform to the provided spec or fail. This is a "hot topic" (if LP topics can really still be "hot") and sees active development in new prolog systems.

Check this out:

https://www.swi-prolog.org/pldoc/man?section=pio

https://github.com/mthom/scryer-prolog/blob/084fc845902f7b43...

20ms both parts https://github.com/Fadi88/AoC/blob/master/2023/day11/code.py

https://github.com/Fadi88/AoC/blob/master/2023/day06/code.py It runs in 200 Ms both parts using python and around 1 Ms using pypy

Same Algo as my python code from earlier, now just using math not search space reduction also blazing fast in micro seconds https://github.com/Fadi88/AoC/tree/master/2023/day06