Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use intermediate representation #3

Open
mristin opened this issue Dec 17, 2020 · 0 comments
Open

Use intermediate representation #3

mristin opened this issue Dec 17, 2020 · 0 comments

Comments

@mristin
Copy link
Owner

mristin commented Dec 17, 2020

Current immediate representation (IR) is crude and the strategies are directly inferred on abstract syntax tree (AST). This approach is quite limiting as it is difficult to reason about better pattern matching at a higher level of abstraction.

Instead of direct matching, introduce three different IRs:

  1. AST of the contracts -> constraint base which contains all the relevant preconditions in an interpretable form. This might be AST, but can be also a different representation; it needs to be further explored.
  2. Dependency graph which represents multi-argument constraints and how they are related.
  3. Flow graph that covers material implications (not A or B which is equivalent to A implies B) and disjunctions (A or B).

This needs more thinking and a literature survey. It is written here as a note for further discussion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant