1. MPS Support | JetBrains
  2. Community
  3. MPS

Using constraints defined on super-concept

Avatar
amirweinberg
Created
I defined constraint (can be parent) on abstract concept, and tried using it on sub-concept. The function didn't work. Moving the constraint definition into the extending concept cause the function to work. This force me to duplicate same constraint on every sub-concept.
Any help?
2 comments
Avatar
Brunni
Created
Comment actions Permalink
Did you try using a non-typesystem-rule instead?

You then can provide a nice error message and perhaps this is also applied to sub-concepts.
0
Avatar
amirweinberg
Created
Comment actions Permalink
Non-typesystem-rule is indeed applied on sub-concept but does not effect completion menu.


Right now I'm taking the following approach: Define the constraint logic as a method in the super-concept behavior and explicitly call this method from sub-concept constraint. This allows me to prevent complex code duplication and leaves (relatively small) burden of adding the call in every sub-concept.
0

Please sign in to leave a comment.