I've seen live template inserting generic implementation for equals() using reflection. I could imagine the same for hashCode and toString.
At least for me these generated methods don't add any value. If I want equals I prefer to write it myself and to determine precisely which variables define the state of my class, if I write toString - I want to see concise description and not full memory dump (that's what the debugger is for). But if you feel more comfortable with standard implementations, you could use the generic versions and rewrite them yourself if the profiling shows them as bottlenecks (I've seen this very rarely). so from me it gets -1 --dimiter "Alain Ravet" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]... > +5 > This is an old request - and battle - : make objects canonical. > > In the meantime, I solved this with a doclet. Not perfect, but good enough. > Integration would be better, though. > > Alain Ravet > > Martin Bayly wrote: > > > I find it tedious to write equals, hashcode and toString methods for > > classes. It would be great if IDEA could do this for me by examing the > > fields of a class and generating/maintaining a default implementation of > > these methods. > _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
