Re: Records -- current status

[Brian Goetz]

This will be an education problem with value types in general, records 
or not.  In fact, in the early days of value types, we observed that, 
because value types can have a more sensible default 
equals/hashCode/constructor/etc, we were worried that people might 
select value types for syntactic reasons.  Hence, in part, splitting 
records off and doing them first, and making it clear that the record 
axis is orthogonal to the value axis.  Of course, people may be confused 
about these new concepts anyway.

On 3/20/2018 12:10 PM, Remi Forax wrote:

I'me afraid that users will select value records to have immutability 
to after discover that they have lost the identity property.
== between a value type and something else return false.