java.lang.__Value ??

Ali Ebrahimi ali.ebrahimi1781 at
Mon Nov 23 18:08:28 UTC 2015


On Mon, Nov 23, 2015 at 8:10 PM, Brian Goetz <brian.goetz at> wrote:

> [ adding background ]
> The __Value type as it currently stands is simply a placeholder for the
> current round of compiler experiments (hence the deliberately horrible
> name).
> In the long run, we need:
>  - A place to put Object methods that pertain to values (e.g., equals and
> hashCode, but not wait and notify)
>  - Possibly a place to put top-level methods that do NOT pertain to Object
> (not completely sure what these would be, but its possible we'll want some,
> perhaps boxing and unboxing would be surfaced here)
>  - Possibly a type to use as a bound in some contexts (though not clear
> this is needed)
>  - Possibly a type to unify what is common between objects and values (the
> current thinking here is something like Objectible / Objectifiable /
> Objectionable / ObjectionYourHonor, which could be an interface implemented
> by both Object and values.)
Or Any


Best Regards,
Ali Ebrahimi

More information about the valhalla-dev mailing list