Affects Version/s: None
Fix Version/s: None
|Field||Original Value||New Value|
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Assignee||Bruno P. Kinoshita [ kinow ]|
[ Hi there,
I thought about why someone would include equals, toString and hashcode in an interface, like in Functor. As java.lang.Object implements such methods, no compile errors are raised.
One possibility for having compile time errors would be create an abstract class with the same methods as abstract. But IMHO this option may not be always valid, and it really only clutters the API.
However, having this in this interface can be helpful for someone interested in implementing a Functor, although this piece of information could be in the project web site, or in a Wiki or something similar. IDE's, like Eclipse, can display the Javadoc for these methods too (sometimes I let the mouse over or click F3 just to see the original code and its Javadoc).
I believe Java java.util.Map interface also contains equals and hashcode, and in the Javadoc you can read what you need to have in mind when creating your Map.
I have no strong opinion for this issue, but thought I could just give my 0.02 cents :)
Cheers, Bruno ]
|Status||In Progress [ 3 ]||Open [ 1 ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|644d 12h 6m||1||Bruno P. Kinoshita||26/Oct/13 15:09|
|2h 49m||1||Bruno P. Kinoshita||26/Oct/13 17:58|
|1m 15s||1||Bruno P. Kinoshita||26/Oct/13 17:59|