Nikolas Göbel

I prefer suggestion 3, because it is no new syntax, just a new type of binding. The "alfredo" use case seems highly confusing, because it breaks the unification intuition (`?person`...

Some more findings, mostly intended as memo. Default can't be something associated with just a symbol. E.g. `(default ?v fallback)` doesn't make sense, because as with negation, defaults need to...

So https://github.com/comnik/declarative-dataflow/commit/1a65b0f98031996e5126d48ae7992d1f3361de19 adds experimental support for something like this. Indeed it is both simpler and more complex than expected. More complex, because (for new-query-engine reasons) default bindings are not just...

There are no decisions made regarding pull, but I have a few thoughts and I'm very happy for input on this as my mind is currently occupied with Datalog-related stuff....

A first step is done in https://github.com/comnik/declarative-dataflow/commit/4a2c8dff1a6e793d9bfacc93e02bc0502945dd19. That commit introduces a `PullLevel` operator which can be used to implement each of the individual streams mentioned above.

Exciting stuff! Yay for separate module, nay for killing the old aggregate test ;) 1. How would that look like? 2. But seems worth it? Or am I missing something?...

With ad51076e2d6494d6173a1ddf742a2c7488824916 there is now a new configuration option to actually keep index traces un-compacted. That would have to be enabled before experimenting with historical queries.

Interesting, I don't get that error from within a CLJS project, but definitely seems like a problem. Will take a look.

A 80/20 solution here would be to add the ability to limit the number of times an attribute might be used (e.g. once), after which the trace will be dropped...

Floating points are experimental, via `Value::Rational32`, but seem to work.