<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<blockquote type="cite" cite="mid:1884486700.20372636.1768848050872.JavaMail.zimbra@univ-eiffel.fr">
<div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000">
<div data-marker="__QUOTED_TEXT__">
<div><br>
</div>
<div>The modifier "component" is too close to the "property"
modifier I wanted to include years ago, it's just to sugary
for its own good.</div>
</div>
</div>
</blockquote>
<br>
You know the rule; mention syntax and you forfeit the right to more
substantial comments....<br>
<br>
<blockquote type="cite" cite="mid:1884486700.20372636.1768848050872.JavaMail.zimbra@univ-eiffel.fr">
<div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000">
<div data-marker="__QUOTED_TEXT__">
<div>I have used HashSet as an example to say that I would
prefer equals/hashCode/toString not to be generated so my
students can launch the debugger to understand why it does
not work as intended.</div>
</div>
</div>
</blockquote>
<br>
"Generation" is not the right level for this discussion, though.
This feature is not a Lombok macro generator; it is a semantic
feature. Can you restate this in terms of what you think such as
class should _mean_? <br>
<br>
<blockquote type="cite" cite="mid:1884486700.20372636.1768848050872.JavaMail.zimbra@univ-eiffel.fr">
<div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000">
<div data-marker="__QUOTED_TEXT__"><br>
<blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><font size="4" face="monospace">But these are all vague
"something could go wrong" worries. Do you have a
concrete point? Are you claiming that there is something
wrong with the design of this feature because of it? Or
are you merely pointing out that "there are risks, and we
should educate people"? </font></blockquote>
<div><br>
</div>
<div>
<div>Nothing is wrong, if the tradeoffs are known and
acknowledge.</div>
<br>
</div>
</div>
</div>
</blockquote>
<br>
OK, that's good! Let's talk about those tradeoffs -- but let's do
so in terms of semantics, not generation?
</body>
</html>