News for hackers. Stuff that matters.
Re:Never Use toString() for Behaviour by nsporillo on Wednesday December 04, 2019 @02:24PM (#21705944)
Lomboks annotation @ToString will automatically generate the typical overridden toString() method based on the fields.
Re:Never Use toString() for Behaviour by chopin on Thursday December 05, 2019 @08:44AM (#21712174)
I just tried this in Java and I ran quickly into circularity issues (one of the fields has an indirect reference to the same object, say a list which the current instance is part of). How does Lombok cope with that?

It's not that easy as I thought (see my sibling comment).

Re:Never Use toString() for Behaviour by chopin on Wednesday December 04, 2019 @04:17PM (#21707115)
Even Object.toString could do this using reflection. If you're worried about the performance, override it. I never understood why this is not the case (doesn't Haskell do something similar?).