On 10/01/2020 03:27, Brian Goetz wrote:
...
I mostly agree that deprecation here is kind of silly, but since
@Deprecated is "just" an annotation, I don't object to it being allowed.
Serialization should be fine, as we go through a similar process for
encoding/decoding fields as default serialization, so the extra field
will be ignored.
That is correct.
Record Serialization will deserialize whatever stream fields that are
described by the stream class descriptor, but only pass the canonical
constructor the stream values that match. Any unmatched stream field
values are effectively discarded ( just like with ordinary object
deserialization ).
-Chris.
