History

Fedor Isakov 54439e255e Refactor typechecking state/cache subsystem. Refactor whe way TypecheckingResultsCache is updated: all mutatiting methods extracted to Update subclass, which is only available to the updater. Make TypecheckingState a regular container for (unit) caches. Make TypecheckingService responsible for managing caches. Extract TypeModuleOwner and TypeModelHandler classes. Get rid of QueryResultsCache, merge into TypecheckingResultsCache. TypeModuleOwner to manage "repository" cache.		2020-08-14 16:57:36 +02:00
..
doc/img	Update readme files.	2018-07-19 15:12:34 +02:00
languages	Ensure rules are created in predictable order, minor refactoring in ProgramFactory.	2020-08-06 17:45:47 +02:00
solutions	Refactor typechecking state/cache subsystem.	2020-08-14 16:57:36 +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.