History

Grigorii Kirgizov 9bbcf6ecef Allow terms to inherit features from ancestor terms Avoides the need to exactly duplicate features of ancestors. Opens possibility to match on super-terms with partially provided (overriden) features. For example, suppose there's `typeParameterized(child: param)` term which is extended by `classifier` and `methodSignature`. Then it becomes possible to write a common rule for both terms, matching on `typeParameterized(param=[Smth])`.		2020-05-21 16:31:36 +03:00
..
doc/img	Update readme files.	2018-07-19 15:12:34 +02:00
languages	Allow terms to inherit features from ancestor terms	2020-05-21 16:31:36 +03:00
solutions	Add a test for AspectClique for the case of asepct with branches	2020-05-11 15:20:37 +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.