-
Notifications
You must be signed in to change notification settings - Fork 155
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
Replace 'equals' and 'hashCode' methods with 'sameState' for mutable objects #152
Comments
jenetics
added a commit
that referenced
this issue
Nov 17, 2016
jenetics
added a commit
that referenced
this issue
Nov 17, 2016
jenetics
added a commit
that referenced
this issue
Nov 17, 2016
jenetics
added a commit
that referenced
this issue
Nov 17, 2016
jenetics
added a commit
that referenced
this issue
Nov 17, 2016
jenetics
added a commit
that referenced
this issue
Nov 17, 2016
jenetics
added a commit
that referenced
this issue
Nov 17, 2016
jenetics
added a commit
that referenced
this issue
Nov 17, 2016
jenetics
added a commit
that referenced
this issue
Nov 17, 2016
jenetics
added a commit
that referenced
this issue
Nov 17, 2016
jenetics
added a commit
that referenced
this issue
Nov 17, 2016
jenetics
added a commit
that referenced
this issue
Nov 17, 2016
jenetics
added a commit
that referenced
this issue
Nov 17, 2016
jenetics
added a commit
that referenced
this issue
Nov 17, 2016
#152: Implement 'sameState' methods.
Branch has been merged into r3.7.0. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some mutable objects are implementing
equals
andhashCode
methods. Like the random engine implementation and some classes in theorg.jenetics.stat
package. They where mainly implemented to make testing easier.The
equals
method is replaced by a newsameState
method, which allows the comparison of the current state of this mutable objects. The currentequals
andhashCode
methods will be marked as deprecated.The text was updated successfully, but these errors were encountered: