History

Fedor Isakov 6c63cb409f Introduce Config component. Make typechecker pref page nicer. Consolidate all typechecking options. A reusable Config app component to be responsible for all level of configurations: default/system/user/ui. Swith to Config interface instead of map<string,Object> for options. Add an UI option to control whether trace is enabled.		2019-10-18 11:58:51 +02:00
..
doc/img	Update readme files.	2018-07-19 15:12:34 +02:00
languages	Handle one more case of finding principal constraints in Query rules with an additional heuristic.	2019-10-15 21:15:38 +03:00
solutions	Introduce Config component. Make typechecker pref page nicer. Consolidate all typechecking options.	2019-10-18 11:58:51 +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.