It makes definition of principal constraint clearer: principal constraint is a constraint that has at least one arg of type node<> and passes to it ruleOrigin in at least one rule. Such constraints are most likely meant to define relations of nodes to terms, e.g. `typeOf` -- which is what we're interested in. At the same time semantics of values inside terms is less defined. TermFeatures are also untyped, and so complete analysis of ValueFeatures would require full code traversal of coderules program to find out whether a value feature is used to carry smth of `node` type. Relevant to MPSCR-62. |
||
|---|---|---|
| .. | ||
| jetbrains.mps.lang.coderules | ||
| jetbrains.mps.lang.controlflow | ||
| jetbrains.mps.lang.smodel.types/generator/template | ||
| jetbrains.mps.lang.typechecking | ||
| jetbrains.mps.logic | ||
| jetbrains.mps.typechecking.annotation | ||
| jetbrains.mps.typechecking.testlang | ||
| jetbrains.mps.typechecking.testlangCycle1/generator/templates | ||
| jetbrains.mps.typechecking.testlangCycle2/generator/templates | ||