History

Grigorii Kirgizov 119daf05d9 Restrict notion of a principal rule to not track unnecessary matches in journal Now principal rule head must include only principal constraints or be empty. Without this restriction journal may include stale chunks which have no information to invalidate them.		2020-02-05 12:29:33 +03:00
..
doc/img	Update readme files.	2018-07-19 15:12:34 +02:00
languages	Restrict notion of a principal rule to not track unnecessary matches in journal	2020-02-05 12:29:33 +03:00
solutions	Fix missed dependencies when computing rule's uniqueTag (from nodes in macro expand)	2020-02-05 12:29:33 +03:00
README.md	Fix paths to images.	2018-07-19 15:17:06 +02:00

README.md

Code Rules - Implementation Notes

Structure

The project modules are separated into several groups to separate levels of abstraction.

Logic

Define fundamental ideas used throughout the implementation, such as «data form» (a.k.a. term), logical variables, and others.

Code rules

Modules in this group define the core concepts of coderules and the logic behind it. This includes constraints, predicates, handlers, as well as code rule templates.

Constraints activation trace view for debugging the process of evaluating constraint rules.

Once finished, constraint rules produce inferred types and type errors, which are added as highlighter annotations to the editor.

Type checking

Defines a custom aspect «types», which is used to store the typing rules in the language source code.

Type checking plugin for MPS provides the actions for checking the types in a currently opened root.

Control flow

Declares only control flow aspect. All functionality is inherited from coderules language.