EvaluatedCandidate class must not be final, because when implementing custom EvolutionEngine, users often want to associate additional data with each EvaluatedCandidate.
For example, if each candidate's fitness is compound fitness from several simulations, user may want (for reporting / logging purposes) store all fitness components in EvaluatedCandidate's custom inherited class.
Currently finality of EvaluatedCandidate & PopulationData classes prevents users from properly implementing custom EvolutionEngine.
EvaluatedCandidate class must not be final, because when implementing custom EvolutionEngine, users often want to associate additional data with each EvaluatedCandidate.
For example, if each candidate's fitness is compound fitness from several simulations, user may want (for reporting / logging purposes) store all fitness components in EvaluatedCandidate's custom inherited class.
Currently finality of EvaluatedCandidate & PopulationData classes prevents users from properly implementing custom EvolutionEngine.