Necessity of equals(Objects) in Operation
Bug #730131 reported by
Philippe Pinard
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| EBSD-Image |
Fix Released
|
Medium
|
Philippe Pinard | ||
Bug Description
Assess if all operations should implement equals(Object)
Revision history for this message
| Philippe Pinard (philippe.pinard) wrote | #1 |
| Changed in ebsd-image: | |
| milestone: | none → 0.2.0 |
| importance: | Undecided → Medium |
| assignee: | nobody → Philippe Pinard (philippe.pinard) |
| status: | New → Fix Committed |
| Changed in ebsd-image: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
It was decided that Operation that an operation should have equals(Object) or equals(Object, Object) but never both. equals(Object) is used when two operations can be assert to be exactly equal, whereas equals(Object, Object) is used when a level of precision is required to say that two operations are equal