I have been scaling back my `data` usage recently ...
# language-proposals
c
I have been scaling back my
data
usage recently precisely because I want to avoid the syndrome to declare one just to get a
toString()
. My current criterion to make something a
data
class is: do I ever want to use instances of this class as a key to a map? (in other words, do I need
hashCode/equals
)? If the answer is no, I use a regular class and I override
toString
manually with my own toString implementation