polonius VS differential-datalog

Correctness prover which uses lifetimes (Polonius).

And, well, polonius (Rust borrow checker magic) I believe is built on datalog-ish concepts: https://github.com/rust-lang/polonius

There is also polonius (https://github.com/rust-lang/polonius) which should replace the borrow checker but does not receive a lot of development resources.

This is eventually going to be a feature-complete compiler, targeting a specific rustc version. I believe the plan is to use polonius [1], presumably as an "optional" feature so they can build a stage 1 without it, use that to build polonius, then build the final compiler with it included.

[1] https://github.com/rust-lang/polonius

E.g. there you may just stop using current borrow-checker and switch to Polonius.

The borrow checker is too dumb (https://github.com/rust-lang/polonius) fixes a lot of this.

It looks like an official borrow checker implementation called Polonius uses it as a dependency, so it makes sense: https://github.com/rust-lang/polonius/blob/981785c101b68ff54...

If you click around a little, you end up on a blog post with this tidbit:

> This project got put together rather suddenly, in response to some work the Rust folks are doing[1] on their new and improved borrow checker.

I don't think I could tell you more than "Frank wrote it to help rust folks who were previously doing work with differential-dataflow directly."

1. https://github.com/rust-lang/polonius/pull/36#issuecomment-3...

Good news is that there's also works going on to relax the restrictions, like polonius. But it seems that it still have a long way to go before it can land in stable Rust...

GCC-rs isn't intended for bootstrapping, it is intended to be an actual fully featured Rust compiler in the future, mrustc is a Rust compiler intended for bootstrapping though. GCC-rs is still very early targeting an older version of the reference compiler without things like a borrow checker, but that's not going to be the case forever. The GCC-rs folks have expressed interest in re-using the borrow checker library used by the reference compiler called polonius enabling them to relatively easily add borrow checking.

Hi,

> I wonder if it lives up to the hype.

We do think so! (disclaimer: I'm a co-founder at Feldera)

To give some more background: We are co-designing/trialing feldera with several industry/enterprise partners from different domains. Our core team also built differential datalog (https://github.com/vmware/differential-datalog) in the past. And while ddlog is used quite successfully in products today, we believe the many lessons we learned with ddlog will help us to build an even better continuous analytics platform. FYI our code is open-source at https://github.com/feldera/feldera if you'd like to try it out.

Also feel free to join our community slack channel (https://www.feldera.com/slack/) if you have more questions.

The relational model (and generally working at the level of sets/collections, instead of the level of individual values/objects) actually makes it easier to have this kind of incremental computation in a consistent way, I think.

There's a bunch of work being done on making relational systems work this way. Some interesting reading:

- https://www.scattered-thoughts.net/writing/an-opinionated-ma...

- https://materialize.com/ which is built on https://timelydataflow.github.io/differential-dataflow/, which has a lot of research behind it

- Which also can be a compilation target for Datalog: https://github.com/vmware/differential-datalog

- Some prototype work on building UI systems in exactly the way you describe using a relational approach: https://riffle.systems/essays/prelude/ (and HN discussion: https://news.ycombinator.com/item?id=30530120)

(There's a lot more too -- I have a hobby interest in this space, so I have a small collection of links)

Tutorial which I didn’t see linked in the README: https://github.com/vmware/differential-datalog/blob/master/d...

This is amazing!

Have you looked at differential-datalog? It's rust-based, maintained by VMWare, and has a very rich, well-typed Datalog language. differential-datalog is in-memory only right now, but could be ideal to integrate your graph as a datastore or disk spill cache.

https://github.com/vmware/differential-datalog

Sort of related, in my mind at least, is differential dataflow, e.g. https://github.com/vmware/differential-datalog

It’s fascinating to see so many different parties converging on Datalog for reactive apps & UI.

- There are several such talks at https://www.hytradboi.com/ (happening this Friday)

- Roam Research and its clones Athens, Logseq, use Datascript / ClojureScript https://github.com/tonsky/datascript

- differential-datalog isn’t an end-to-end system, but is highly optimized for quick reactivity https://github.com/vmware/differential-datalog

- Datalog UI is a Typescript port of some of differential-datalog’s ideas https://datalogui.dev/

Rust related https://github.com/vmware/differential-datalog

Actually, that makes me wonder whether or not differential datalog falls under that umbrella, and if it could be applied in the same way Compose is.