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)
This commit is contained in:
Grigorii Kirgizov 2020-06-08 18:35:42 +03:00
parent f3d62dbc94
commit af3170e428
1 changed files with 0 additions and 1 deletions

View File

@ -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)
}