rea1 / karp Goto Github PK

Currently, the runtime errors for language constructs point to the code that does the internal implementation. For example, when looking up a mapping with a key that is not in the domain, it triggers "no value for key" messages instead of "element not in the domain".

A positive literal for example x1 should be able to be used in the same way as the variable x1 and vice versa. The negative literal ¬x should be able to be created with (not x) and (not ¬x) should evaluate as x.

There could be duplicated literals from the same clause. For example, there are two x_1 in the clause (x_1 v x_1 v ¬x_2) and they should be treated as different objects that are not equal?. However, we also need to consider the consequences of making them not equal?.

To create a path in the current language design, the user needs to create a set of edges and a set of vertices and combine them as a subgraph, which is unnatural. A simple system of subtyping does not always work as a lot of times we want to interpret the same structure differently. For example, we might want to impose a certain order on a set and make it a list.