History

Grigorii Kirgizov cc9c4c54b3 Specify notion of required nodes: separately for tmpl application & for UpdatesRecorder Too many nodes get into tmpl application process, which is unnecessary. Many of those nodes are required actually only for correctly tracking changes to nodes with WatchingTypecheckingStrategy. Now implicitly required only nodes which are mentioned inside constraint arguments. In other cases user must require them explicitly.		2020-10-23 12:26:30 +02:00
..
doc/img	Update readme files.	2018-07-19 15:12:34 +02:00
languages	Specify notion of required nodes: separately for tmpl application & for UpdatesRecorder	2020-10-23 12:26:30 +02:00
solutions	Specify notion of required nodes: separately for tmpl application & for UpdatesRecorder	2020-10-23 12:26:30 +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.