-
Enhancement
-
Resolution: Done
-
Major
-
None
-
None
-
2021 Week 07-09 (from Feb 15)
-
3
-
Undefined
-
NEW
-
NEW
The current implementation that turns a constraint collector into a Drools accumulate function is somewhat inefficient. With the recent improvements to Drools, we should be able to get rid of our own undo map, leading to lower memory consumption and potentially also performance improvements.
- relates to
-
PLANNER-2333 Data classes/Records: Exception "Undo does not exist" (don't rely on equals()/hashcode() if identity suffices)
- Resolved