History

Grigorii Kirgizov c6889be4e7 Consider possible errors at rule generation stage as non fatal and produce Program with some rules dropped (fixes MPSCR-38) New Result.RECOVERED case-class is added which collects errors but doesn't fail. Currently errors are collected but not reported.		2020-02-06 01:02:50 +03:00
..
doc/img	Update readme files.	2018-07-19 15:12:34 +02:00
languages	Consider possible errors at rule generation stage as non fatal and produce Program with some rules dropped (fixes MPSCR-38)	2020-02-06 01:02:50 +03:00
solutions	Consider possible errors at rule generation stage as non fatal and produce Program with some rules dropped (fixes MPSCR-38)	2020-02-06 01:02:50 +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.