<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<font size="4" face="monospace">First, a gentle reminder that I did
ask "please, let's not discuss syntax." It is way too early for
that; we haven't even had a discussion on the value of the ideas
yet. But people can't help but obsess on syntax, so I'll answer,
but please let's let this thread end here. <br>
<br>
Yes, we considered matching on name and type only. There is
nothing about that approach that makes it unworkable, but it is
less reliable, and subjectively, seems to be more likely to feel
"magic" or "action at a distance" to the Java developers we showed
this to. By comparison, the overhead of the `component` modifier
is small; it is purely horizontal rather than vertical, and admits
no question about which fields are component fields or not. It
also admits greater flexibility for users (under the implicit
approach, we'd almost certainly want to error out if the names
matched but the types didn't; with the explicit version, we can
accept examples like the AlmostRecord in the writeup.) <br>
<br>
Basically: the value of the clarity seems to outweigh the value of
the concision. )(And, as you point out, a new modifier would
still be needed for "not component" in that case.) <br>
<br>
</font><br>
<div class="moz-cite-prefix">On 1/13/2026 10:25 PM, Ganapathi Vara
Prasad wrote:<br>
</div>
<blockquote type="cite" cite="mid:CAPwa2fnOUB8a1-rP9T71JZOtky8d-3gDzM5aeuscq9oTvL0vUw@mail.gmail.com">
<div dir="auto">Hello Brian,
<div dir="auto"><br>
</div>
<div dir="auto">Thank you for thinking on this feature. I want
to better understand the thought process behind marking all
fields that are part of the component state instead of only
the derived fields. Something like this:</div>
<div dir="auto"><br>
</div>
<div dir="auto">```</div>
<pre>class Point(int x, int y) {
private final int x;
private final int y;
private final derived double norm;
Point {
norm = Math.hypot(x, y);
}
public double norm() { return norm; }
// derived implementation of x and y accessors
// derived implementation of equals, hashCode, toString
}
```</pre>
</div>
</blockquote>
<br>
</body>
</html>