mps-coderules/coderules
Clement de La Bourdonnaye 61bc21c1d0 Build script: make plugin packaging the first in layout
This fixes dependencies, as the build language uses the first layout for a given module defined in the build model
Having coderules-ideaplugin folder before the plugin changed the way dependencies generate their build script, while the artifacts stayed with the same structure
2023-12-18 11:56:22 +01:00
..
devkits/jetbrains.mps.devkit.aspect.types Introduce language j.m.l.types to contain aspect-related generator mappings 2021-08-17 09:29:21 +02:00
doc/img Update readme files. 2018-07-19 15:12:34 +02:00
languages Make all expand template params optional 2023-10-16 11:55:32 +02:00
solutions Build script: make plugin packaging the first in layout 2023-12-18 11:56:22 +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.