Pete Vilter

**Repro** * Put some rules in the fiddle that call infinite "virtual" relations like `base.lt` **Expected** * no errors in console **Actual** Errors in console: Maybe "error" and "infinite" need...

disabled in https://github.com/vilterp/datalog-ts/pull/130 https://github.com/vilterp/datalog-ts/pull/130/files#diff-89ebce8086202c48050e22f7a707349c38feb39217265501a159518da4dc124dR12

Lord knows how to do this in Monaco. lol

Graphviz was removed because it conflicted with `react-flow`, which was added for the drag-n-drop graph editor.

**Repro** * In the LWB, delete rules from datalog editor on the right pane **Expected** * Syntax and variable highlighting stops working on the right **Actual** * Variable highlighting (and...

simple interpreter: variables not declared in head can still have bindings

1

See https://github.com/vilterp/datalog-ts/pull/87/commits/c95bd72c3ac5a770e3553c79641a31863c530eb7 Had to rename `I` to `RuleID` because `I` had a binding from somewhere else. This shouldn't happen

Calling rule: ``` hl.Segment{type: T, id: I, span: S, highlight: H} :- hl.segmentInt{type: T, id: I, span: S, highlight: H} | hl.segmentString{type: T, id: I, span: S, highlight: H} |...

Via some kind of currying. Blocked by not supporting a left-recursive grammar… Last item for parity with hardcoded FP.

If there are two definitions in scope, both are highlighted as the definition. Need some logic to choose the closer one, but not sure how to specify this in datalog...

**expected:** * variables are only in scope after they're defined **actual:** * in scope where they're defined **example**  `y` should not be an option here, since it's being defined....