From af3170e428e750f0669abbe74d6c73bbb9607fc2 Mon Sep 17 00:00:00 2001 From: Grigorii Kirgizov Date: Mon, 8 Jun 2020 18:35:42 +0300 Subject: [PATCH] Remove invalid assert from incremental processing Some time ago "mixed" matches (with both principal and non-principal heads) were allowed and are handled by Journal. So now principal constraints can lead to non-principal matches, which renders assert invalid. (Relevant for MPSCR-62) --- .../mps/logic/reactor/core/internal/ConstraintsProcessing.kt | 1 - 1 file changed, 1 deletion(-) diff --git a/reactor/Core/src/jetbrains/mps/logic/reactor/core/internal/ConstraintsProcessing.kt b/reactor/Core/src/jetbrains/mps/logic/reactor/core/internal/ConstraintsProcessing.kt index e2b32b5f..56ca1506 100644 --- a/reactor/Core/src/jetbrains/mps/logic/reactor/core/internal/ConstraintsProcessing.kt +++ b/reactor/Core/src/jetbrains/mps/logic/reactor/core/internal/ConstraintsProcessing.kt @@ -235,7 +235,6 @@ internal class ConstraintsProcessing(private var dispatchingFront: Dispatcher.Di if (isFront() || !active.isPrincipal()) { matches } else { - assert( matches.all { it.isPrincipal() } ) execQueue.postponeFutureMatches(matches) }