mps-coderules/coderules/languages/jetbrains.mps.logic/languageModels
Fedor Isakov e8a19249e6 Migration to replace spliced LogicalItemExpression on a list node.
Usually one uses Splice with LogicalItemExpression wrapping a logical variable.
Using LogicalDataForm wrapping same variable makes Splice unnecessary.
In order to keep code readable these are wrapped again in a cons list.
In general, one should avoid using bare LogicalDataForm, as these are
indistiguishable from normal LogicalVariable.
2020-04-13 17:58:33 +02:00
..
actions.mps Restructuring the project: consolidate code, moving samples away. 2018-07-14 17:22:07 +02:00
behavior.mps Migration to replace spliced LogicalItemExpression on a list node. 2020-04-13 17:58:33 +02:00
constraints.mps Document j.m.logic language. Rearrange virtual packages. 2020-04-13 17:58:33 +02:00
editor.mps Introduce construct to directly insert term constructor in data form. 2020-04-13 17:58:33 +02:00
intentions.mps Run migrations with MPS 2019.2 EAP3. 2019-07-26 17:27:18 +02:00
jetbrains.mps.logic.enumMigration.mps Migration: "update versions in descriptors". 2019-07-30 11:49:26 +02:00
migration.mps Migration to replace spliced LogicalItemExpression on a list node. 2020-04-13 17:58:33 +02:00
structure.mps Migration to replace spliced LogicalItemExpression on a list node. 2020-04-13 17:58:33 +02:00
typesystem.mps Document j.m.logic language. Rearrange virtual packages. 2020-04-13 17:58:33 +02:00