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
..
controlflow.mps	Manually migrate all queries to new table format.	2020-04-23 10:15:39 +02:00
jetbrains.mps.baseLanguageExt.behavior.mps	Switch to 2018.3 RC. Apply all migrations.	2018-11-28 16:48:59 +01:00
jetbrains.mps.baseLanguageExt.constraints.mps	Restructuring the project: consolidate code, moving samples away.	2018-07-14 17:22:07 +02:00
jetbrains.mps.baseLanguageExt.editor.mps	Apply automatic migrations.	2020-05-09 15:04:25 +02:00
jetbrains.mps.baseLanguageExt.structure.mps	Restructuring the project: consolidate code, moving samples away.	2018-07-14 17:22:07 +02:00
jetbrains.mps.baseLanguageExt.types.mps	Change semantics of implicit ListFeature: treat as wildcard, not as empty list	2020-05-21 16:38:36 +03:00
jetbrains.mps.baseLanguageExt.typesystem.mps	Restructuring the project: consolidate code, moving samples away.	2018-07-14 17:22:07 +02:00