Moving from VVT to the L-world value types (LWVT) (original) (raw)
John Rose john.r.rose at oracle.com
Mon Feb 26 23:41:16 UTC 2018
- Previous message (by thread): Moving from VVT to the L-world value types (LWVT)
- Next message (by thread): Moving from VVT to the L-world value types (LWVT)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Feb 20, 2018, at 9:13 PM, Ali Ebrahimi <ali.ebrahimi1781 at gmail.com> wrote:
Why not have new NonNullable marker interface for marking (new/legacy) value types. We can have nullable and non-nullable types. New (true) value types can implements NonNullable interface by default. By this we can support non-nullable reference types later if want.
If you were to develop this idea into a full proposal, I think you'd find an unsatisfactory number of limitations and paradoxes. Nullability is a lattice cofactor, not an inheritance root. — John
- Previous message (by thread): Moving from VVT to the L-world value types (LWVT)
- Next message (by thread): Moving from VVT to the L-world value types (LWVT)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]