History

Fedor Isakov fa7532f34f Include origin features's hash to requiredHash when building rules. This enables to adequately reflect changes in the model when it is updated by editor actions, such as "side transform". Three tests was broken as the result of this fix and are disabled http://127.0.0.1:63320/node?ref=r%3A8d22f6d9-72f0-49ec-92ee-027a87fbedd4%28jetbrains.mps.baseLanguageExt.test.incremental%40tests%29%2F3095008005741803340		2020-01-02 17:42:38 +01:00
..
doc/img	Update readme files.	2018-07-19 15:12:34 +02:00
languages	Include origin features's hash to requiredHash when building rules.	2020-01-02 17:42:38 +01:00
solutions	Include origin features's hash to requiredHash when building rules.	2020-01-02 17:42:38 +01: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.