Add an IFitness Variant to Compute Fitness for a Collection of Chromosomes on a Vector Processor #136
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
** THIS PR IS INCOMPLETE, SPECIFICALLY IN TEST COVERAGE. **
This PR is a draft implementation of the
IVectorFitnessconcept we discussed in email. It has come out much like what I suggested, except the vector extension uses an abstract implementation ofIFitnessand a runtime type check instead of alteringIFitness, for backward compatibility.It is agnostic wrt vector processing (GPU) libraries the user may use.
I'm looking for questions & Feedback on this approach before I extend the tests.
One question: Do I need to worry about consumers of
IFitnessother thanGeneticAlgorithmthat might expect aVectorFitnessto work polymorphically?This also includes the change for issue #135. Thanks!