jlrs VS scryer-prolog

And in the rare case that Julia isn't enough, Julia-Rust interop is pretty good! Julia can call Rust using ccall and Rust can call Julia using the jlrs crate.

Github

While there is Jlrs , there is no seamless and easy way to call Rust. We need 'rustcall' on a level of 'pycall'.

I have a roadmap issue with some ideas/designs/arguments https://github.com/Taaitaaiger/jlrs/issues/66

An option for Julia/Rust interop is jlrs

jlrs automates some of this, using stack frames to garantee that Julia won't gc the references you're holding in Rust. It also provides ways to coerce Rust structs into Julia structs, and it does a bunch of other stuff I'm probably forgetting.

Github

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            |