Data Oriented Programming, Beyond Records

[Brian Goetz]

>
> 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.

You know the rule; mention syntax and you forfeit the right to more 
substantial comments....

> 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.

"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_?

>
>     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"? 
>
>
> Nothing is wrong, if the tradeoffs are known and acknowledge.
>

OK, that's good!  Let's talk about those tradeoffs -- but let's do so in 
terms of semantics, not generation?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/amber-spec-experts/attachments/20260119/9104a959/attachment.htm>