mps-coderules/samples/mpscore/solutions/jetbrains.mps.baseLanguageE.../models
Grigorii Kirgizov e2b3c21b2f Change semantics of implicit ListFeature: treat as wildcard, not as empty list
Motivation is that implicit (non-overriden) list features must unify
with list of any length. Consider an example:
`classifier(cls: node-ptr/A/) = classifier(cls: node-ptr/A/ param: [B,C])`
With previous approach it would fail, which seems counter-intuitive to me.
So, if empty list (e.g. of type parameters) is meant, then it must be
specified explicitly.

There's one thing to remember, though: such wildcard list features
won't match with MetaLogicalArrays in rule heads.
(e.g. see dpromote_* rules and consider what happens when
a classifier with unbound `parameter` feature comes in)
2020-05-21 16:38:36 +03:00
..
jetbrains.mps.baseLanguageExt.test.code.features.mps Add typechecking for AlternativeType. Move & refactor genDecl macro a bit. 2020-05-21 16:38:30 +03:00
jetbrains.mps.baseLanguageExt.test.code.generics.mps Apply automatic migrations. 2020-05-09 15:04:25 +02:00
jetbrains.mps.baseLanguageExt.test.code.staging.mps Apply automatic migrations. 2020-05-09 15:04:25 +02:00
jetbrains.mps.baseLanguageExt.test.code.thinlet.mps Apply automatic migrations. 2020-05-09 15:04:25 +02:00
jetbrains.mps.baseLanguageExt.test.dummy.mps Repackage typechecking tests to separate module. 2019-11-06 21:14:12 +01:00
jetbrains.mps.baseLanguageExt.test.features@tests.mps Change semantics of implicit ListFeature: treat as wildcard, not as empty list 2020-05-21 16:38:36 +03:00
jetbrains.mps.baseLanguageExt.test.generics@tests.mps Apply automatic migrations. 2020-05-09 15:04:25 +02:00
jetbrains.mps.baseLanguageExt.test.incremental@tests.mps Apply automatic migrations. 2020-05-09 15:04:25 +02:00
jetbrains.mps.baseLanguageExt.test.thinlet@tests.mps Apply automatic migrations. 2020-05-09 15:04:25 +02:00
jetbrains.mps.baseLanguageExt.test.types@tests.mps Apply automatic migrations. 2020-05-09 15:04:25 +02:00