prolog
chalk
prolog | chalk | |
---|---|---|
14 | 25 | |
539 | 1,768 | |
- | 0.6% | |
5.6 | 7.0 | |
3 months ago | 28 days ago | |
Go | Rust | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
prolog
-
Mangle, a programming language for deductive database programming
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.
- Golog library/language?
-
State machines and reconciliation loops
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.
-
Let's philosophize a bit :-)
You may also be interested in this Prolog interpreter in Go: https://github.com/ichiban/prolog
-
Interpreters built in Go
There have been several Prolog interpreters written in Golang. This one appears to be most active: https://github.com/ichiban/prolog .
-
The Power of Prolog
For Go, you have prolog as a scripting engine https://github.com/ichiban/prolog
- Prolog runtime for aws lambda?
- Prolog Go Library
-
Hacker News top posts: Jan 27, 2022
An embeddable Prolog scripting language for Go\ (2 comments)
- An embeddable Prolog scripting language for Go
chalk
-
Why did Prolog lose steam? (2010)
The Rust compiler uses a Prolog-like query language internally for type checking generic requirements and traits: https://github.com/rust-lang/chalk
-
Why doesn't rust-analyzer reuse infrastructures of rustc?
rust-analyzer already uses chalk (https://github.com/rust-lang/chalk) which should replace the current trait resolver.
-
Why use Rust on the backend? by Adam Chalmers
Well it's quite easy to come to that conclusion: The code compiles with rustc, which is currently the reference implementation. If rust-analyzer does not match rustc's behavior it's an issue in their implementation. That written it's not that easy to fix as it's related to how rust-analyzer resolves types/traits. rust-analyzer uses chalk for this, which is known to be incomplete/diverging from the RFC'ed behavior. Now one could argue that we can simplify diesel to the point where it works will with rust-analyzer/chalk, but that would result in basically removing core diesel features that exist way longer than rust-analyzer.
-
Why has functional programming become so popular in non-academic settings?
> Not all of those things work well in the real world. E.g. logic programming (prolog) is cool but ultimately never really caught on.
It does have its niches though. For example, there is a trait solver for Rust called Chalk that uses a Prolog-inspired language because trait bounds basically define a logic:
https://github.com/rust-lang/chalk
-
General mathematical expression analysis system
Maybe something in the prolog/datalog direction could be useful? Notably Rust has Chalk to help with trait resolution ("Chalk is a library that implements the Rust trait system, based on Prolog-ish logic rules.")
-
Useful lesser-used languages?
There has been work to implement part of the Rust typing logic in the Chalk Engine which uses a prolog-ish syntax to describe its rules.
-
Can you have a function return different types known at compile time
That's something Chalk is trying to tackle.
-
Compile time wins today
We probably will see all of them at some point -- polonius is a current effort to make the borrow checker accept more valid programs, in a way that also simplifies the logic and is probably a bit faster than the current NLL system, chalk is an attempt to do a similar thing for the trait system, and cranelift is a project that seeks to replace the LLVM codegen backend. But obviously, these are very large and complex projects that are gonna take some time.
-
What is the difference between associated types and generics?
Do Rust developers realize that? Oh, yes, absolutely, that's why we have this:
-
Question about Trait Bounds (from Rust for Rustaceans)
For me an attempt to write where HashMap: FromIterator and then use new and insert was totally bizzare because currently rustc is pretty primitive and doesn't do super-complex machinery needed to do what you want. Chalk may fix that one day, but it's nowhere near to being ready for inclusion into rustc thus I wouldn't even attempt to do what you tried to do… but that's not something you are supposed to know before reading this book!
What are some alternatives?
go-python - naive go bindings to the CPython2 C-API
polonius - Defines the Rust borrow checker.
go-lua - A Lua VM in Go
miri - An interpreter for Rust's mid-level intermediate representation
OPA (Open Policy Agent) - Open Policy Agent (OPA) is an open source, general-purpose policy engine.
lccc - Lightning Creations Compiler Frontend for various languages
gval - Expression evaluation in golang
pny1-assignment - College assignment writing in which I ramble about type classes and dependent types.
otto - A JavaScript interpreter in Go (golang)
expr - Expression language and expression evaluation for Go [Moved to: https://github.com/expr-lang/expr]
scryer-prolog - A modern Prolog implementation written mostly in Rust.
unsafe-code-guidelines - Forum for discussion about what unsafe code can and can't do