History

Fedor Isakov c797b5d2ad Breaking change: logical vars must be declared by constraint rule that uses them. Stronger rules for logical variables scope: constraint rule can't reference logical variable defined in another constraint rule. Logical variable definitions are localized to ConstraintRule template. Simplify/cleanup the logic of searching for available logical variables.		2019-10-25 22:45:55 +02:00
..
doc/img	Update readme files.	2018-07-19 15:12:34 +02:00
languages	Breaking change: logical vars must be declared by constraint rule that uses them.	2019-10-25 22:45:55 +02:00
solutions	Introduce dependency to Config in typechecking options and service. Avoid relying on static getInstance() method to access Config.	2019-10-23 15:39:17 +02: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.