prolog VS expr

Other resources for logic programming and Go:

ichiban/prolog - ISO Prolog interpreter in pure Go, getting close to v1: https://github.com/ichiban/prolog

trealla-prolog/go - ISO Prolog interpreter embedded via WASM: https://github.com/trealla-prolog/go

guregu/pengine - library for interfacing with Pengines (SWI-Prolog's RPC protocol): https://github.com/guregu/pengine

biscuit-auth/biscuit-go - Biscuits are a fancy auth token with a little Datalog engine: https://github.com/biscuit-auth/biscuit-go

I'm a big fan of logic programming. We've been seeing a small resurgence of interest in it (for example Yarn using Prolog made some waves) and I have some optimism for its future.

fully native Prolog, or embedded? I am very familiar with Go, so I was intrigued to see ichiban/prolog. This might enable me to leverage some existing libraries (GitHub, git, etc) and save Prolog for the logic that drives them.

You may also be interested in this Prolog interpreter in Go: https://github.com/ichiban/prolog

There have been several Prolog interpreters written in Golang. This one appears to be most active: https://github.com/ichiban/prolog .

For Go, you have prolog as a scripting engine https://github.com/ichiban/prolog

An embeddable Prolog scripting language for Go\ (2 comments)

Not diminishing the article at all, there's massive value I've gained from leveraging this runtime solution in multiple projects: https://github.com/antonmedv/expr

The language is easy enough for people to pick-up.

Uses the [expr](https://github.com/antonmedv/expr) language to achieve this and I've been super happy with the results.

I have been using expr (https://github.com/antonmedv/expr) to do something like this for a while. no complains so far.

If you wanted it to not require putting in the operation first and just accept string equations (without using something like https://github.com/antonmedv/expr) you could parse, tokenize and then process the input.