3 ms·
Is there a more precise description of the runtime semantics anywhere? “A variant of Datalog” is helpful but doesn’t say much. For instance, it looks like ever
by evincarofautumn 10y ago
Is there a more precise description of the runtime semantics anywhere? “A variant of Datalog” is helpful but doesn’t say much.
For instance, it looks like every “commit” is essentially a sequence point that produces a step in the “fixpointer”—and from that terminology I guess Eve is Turing-complete, unlike Datalog? Do you test all patterns at every commit, or only those whose dependencies have changed? And if the latter, then how do you track such dependencies? Are they fully specified declaratively by queries? And what is the granularity—per term, per database?
- anewhnaccount 10y agoThe semantics are similar to Dedalus, which is compared to Datalog here: https://www.youtube.com/watch?v=R2Aa4PivG0g https://www.youtube.com/watch?v=R2Aa4PivG0g
- evincarofautumn 10y agoThat was an excellent talk, thanks. It cleared up a lot of details about the paradigm for me. That said, now I’m more interested in Dedalus/bloom than Eve. :P