natas_hw
/
mps-coderules
mirror of https://github.com/JetBrains/mps-coderules
0
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
mps-coderules/coderules
History
Fedor Isakov 9c616971e1 Ensure all relevant languages are searched for aspects. 
It might be necessary to look a little further into the input node's
referenced nodes to gather all relevant models for recovering
types aspects. Example: a type in BL may extend another BL type
parameterized by a non-BL type, such as node<>.
 		2020-11-24 13:41:24 +01:00
..
doc/img Update readme files. 2018-07-19 15:12:34 +02:00
languages Fix coderules generator, avoid referrences to transient models in types. 2020-11-24 13:41:24 +01:00
solutions Ensure all relevant languages are searched for aspects. 2020-11-24 13:41:24 +01: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.

Activation trace

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.

Example of a typing rule

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.