You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: DSV graph should notify updater when cycles are formed or broken
Previously, the updater only considered nodes that were changed from an edge insertion or deletion. However, an edge insertion/deletion can also change the looped status of a disconnected node. For example, if we have a -> b and b -> a, and we remove a -> b, only b is marked as changed. This is incorrect, since a changed indirectly, since it is no longer looped. Thus, the graph implementations now mark any nodes whose SCC change from singleton to multinode (looped) and vice-versa.
Copy file name to clipboardExpand all lines: core/src/main/java/ai/timefold/solver/core/impl/domain/variable/declarative/BaseTopologicalOrderGraph.java
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ public interface BaseTopologicalOrderGraph {
29
29
30
30
/**
31
31
* Returns a tuple containing node ID and a number corresponding to its topological order.
32
-
* In particular, after {@link TopologicalOrderGraph#commitChanges()} is called, the following
32
+
* In particular, after {@link TopologicalOrderGraph#commitChanges(java.util.BitSet)} is called, the following
Copy file name to clipboardExpand all lines: core/src/main/java/ai/timefold/solver/core/impl/domain/variable/declarative/DefaultTopologicalOrderGraph.java
Copy file name to clipboardExpand all lines: core/src/main/java/ai/timefold/solver/core/impl/domain/variable/declarative/DefaultVariableReferenceGraph.java
0 commit comments