Kauê Hunnicutt Bazilli

Actually, meta-interpreters aren't that hard to do because Prolog is homoiconic. This is a great idea and we could have much better errors already with a small meta-interpreter. This wouldn't...

That is phenomenal, but then we would have a bootstrapping issue: how to parse the parser? We could implement the parser in a "easy to parse" subset of Prolog, and...

You could only have negation and not cut (some Datalog systems do this for example). That would be a non-monotonic but pure logic I guess.

I actually like the current behavior, but it may be because I've been used to it for years. I don't think the argument should be the module name instead of...

See also previous attempt at this: #2407.

There is no good concept of "platform independent path string", that's why Rust uses an "opaque struct" to represent this. [This is also the case in other languages like Python](https://docs.python.org/3/library/pathlib.html)....

Also, it seems you use Windows @rotu, is that right? Scryer Prolog has a real lack of support on Windows because we have basically no recurrent contributor that uses Windows...

> [...] most of the time, they can indeed be spelled as strings. This ignores the important point I brought up that paths are in general not UTF-8 (see Rust's...

> You misunderstand me. In Python, [pathlib](https://docs.python.org/3/library/pathlib.html#pure-paths) uses / as an OS-agnostic path-joining operator. Note too that internal forward slashes get eventually normalized: I do understand that, I've used pathlib...

Bytes would allow having `0xFF` bytes for example, which is invalid UTF-8. I guess just generate some random uniform bytes and see if they round-trip.