-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Built in operator support #30
Comments
Could you give an example of what you would like to see? |
User should be able to use same phenotype implementation with different crossover or mutation operators. With the current state of the library one should write separate phenotype implementations for each operator. |
I understand where you're coming from. Implementing this feature could potentially impact the API of the library a lot, and in my opinion (feel free to disagree or persuade me otherwise) is better suited for a version 2.0 of the library (see also #23). In the meantime, I just pushed an example (7e2b959) of how you can work around this in a fairly ergonomic manner. I would gladly implement your suggestion, but I don't think I'll find the time to do it very soon. |
You are right. This would require API breaking changes. One implementation idea is to use associated types for these operators. |
Hi there.
It would be nice to have pluggable crossover and mutation operators and implementations of well known operators.
The text was updated successfully, but these errors were encountered: