History

Grigorii Kirgizov 3eccaf81a1 Introduce occurrence store as cache for their reuse in Queries strategy It's important that program that uses occurrences from cache shouldn't include rules that could produce their duplicates. So implementation of occurence cache includes 2 parts: on reactor level & in ProrgramFactory. When RuleBuilders are produced, cache is queried whether there're already occurrences associated with the rule template in question. If so -- then those RuleBuilders are not included into the program (as well as all RuleBuilders required by it).		2020-12-15 17:59:05 +03:00
..
doc/img	Update readme files.	2018-07-19 15:12:34 +02:00
languages	Introduce occurrence store as cache for their reuse in Queries strategy	2020-12-15 17:59:05 +03:00
solutions	Introduce occurrence store as cache for their reuse in Queries strategy	2020-12-15 17:59:05 +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.