flamingo-lang / flamingo Goto Github PK

In a dependently-typed language like Coq, Idris, or Formality.

With Satisfiability-Modulo-Theory.

We should be able to output really nice Typescript definitions to go with compiled programs for the queries and actions.

🗓 Start Date: 2020-03-31

🗓 End Date: 2020-04-10

📈 Progress (0-1): 0.5

📝 Dependencies: #1, #2

🧮 Group: custom_group

https://github.com/domoritz/wasm-clingo is deprecated.

I'd like to benchmark my Datalog implementation against Clingo and DDLog. I should also consider handwritten differential-dataflow, but that might be tricky.

Currently there's no way to add objects at runtime to Flamingo. In the first prototype, we had this feature, and it was pretty critical for several encodings.

Can hardly call it ALM without it!

The Elm community is most likely interested in this combination of expressiveness and correctness. I should write ports between Flamingo and Elm.

The trick will be code generation similar to #6.

This is related to how defined fluents work. Essentially, any negative constraints are removed from the program at runtime, so you have to be careful not to end up with accidentally partial functions.

At the very least need one for VS Code, one for Highlight.js, and one for Repl.it.

Using this paper as a guide: https://dl.acm.org/doi/10.1145/1552309.1552311

This will help modeling sooooo much.

Many virtual objects come and go from a domain, but ALM wasn't really designed with them in mind. What's the best way to handle them?

In the documentation, in the intro, there is

axioms
    occurs(A) causes open(Menu) if
        instance(A, open_menu),
        target(A) = Menu.

    occurs(A) causes open(Menu) if
        instance(A, open_menu),
        target(A) = Menu.

The two blocks look the same. Should that second one be close, rather than open?