All Classes and Interfaces

Class
Description
 
 
 
This class has two direct children: AbstractIndexedIfExistsNode and AbstractUnindexedIfExistsNode.
 
There is a strong likelihood that any change to this class, which is not related to indexing, should also be made to AbstractUnindexedIfExistsNode.
There is a strong likelihood that any change to this class, which is not related to indexing, should also be made to AbstractUnindexedJoinNode.
This class has two direct children: AbstractIndexedJoinNode and AbstractUnindexedJoinNode.
 
 
 
 
There is a strong likelihood that any change made to this class should also be made to AbstractIndexedIfExistsNode.
There is a strong likelihood that any change made to this class should also be made to AbstractIndexedJoinNode.
 
 
 
 
 
 
 
 
FP streams implementation of ScoreDirector, which only recalculates the Score of the part of the working solution that changed, instead of the going through the entire PlanningSolution.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
An indexer for entity or fact X, maps a property or a combination of properties of X, denoted by indexProperties, to all instances of X that match those properties, depending on the the indexer type (equal, lower than, ...).
 
Index properties are cached in tuples and each tuple carries its unique instance.
 
 
 
 
 
 
 
 
A tuple is an out tuple in exactly one node and an in tuple in one or more nodes.
 
Different from LinkedList because nodes/indexes are allowed to directly reference TupleListEntry instances to avoid the lookup by index cost.
An entry of TupleList