Grigorii Kirgizov 8629e5abfc Properly handle non-principal rules with origins in incremental algo ... Fixes IncrClassHierarchy.modifyClsHierarchyTypeParams test. Key point is that changes to rules causing their regeneration must be reflected in program. There appeared to be cases when it's not true. It's a case of non-principal rules with origins. Such rules are called "weak principal" rules. Matches of weak principal rules are not recorded in Journal (as is for principal rules), but instead they become part of their parent MatchChunk. (In essense, tags of weak principal rules are recorded in parent chunk). With this, when a weak principal rule changes, matches of all principal rules whose computation depends on them are correctly invalidated. (Example rules: findHierarchy_Classifier) Relevant for MPSCR-62.		2020-07-01 14:36:48 +03:00
..
src	Adjust nullability contract in occurrence matcher.	2020-02-28 17:42:54 +01:00
test	Properly handle non-principal rules with origins in incremental algo	2020-07-01 14:36:48 +03:00
Test.iml	Update Kotlin to 1.3.70 for Reactor lib.	2020-06-25 14:30:31 +02:00
pom.xml	Bump up reactor version to 0.9.14.	2019-09-30 16:31:59 +02:00