Records -- current status

[Brian Goetz]

>
> So add all this up and we have /three/ kind of finalness for fields:
>
> - by default mutable, but you can change it
> - by default final, and you can't change it
> - (and now) by default final, but you can change it
>
> This seems like quite a bad situation to me.
>

I think what you are really saying here is: if you want immutable 
records, wait for value records, don't try to cram them in early? Then a 
record inherits the finality of the class kind that it is describing.  
And same with field accessibility.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/amber-spec-experts/attachments/20180320/d3cc574b/attachment.html>