The client can now specify how the generation of solutions for the next iteration is calculated, having in regards the current generation and the newly created one.
By default, the generation for the next iteration is the new one, but this could be refined, to create a better generation, taking in accound more attributes of the solutions found in both of them.
Coverage decreased (-0.8%) to 86.416% when pulling d2ae36c9f33730987815e8073408394ae8e101c7 on 24 into c538d4c238b04e69c767897df3d05e4414b52cd5 on master.
PR for #24
The client can now specify how the generation of solutions for the next iteration is calculated, having in regards the current generation and the newly created one.
By default, the generation for the next iteration is the new one, but this could be refined, to create a better generation, taking in accound more attributes of the solutions found in both of them.