JEP 401: Value Objects (Preview) merged to OpenJDK master
1–10 of 185 posts
Re: JEP 401: Value Objects (Preview) merged to OpenJDK master
#22934 commits OMG... huge work.
Re: JEP 401: Value Objects (Preview) merged to OpenJDK master
#3How much of Valhalla is this? 50% of it? 90% of it?
Re: JEP 401: Value Objects (Preview) merged to OpenJDK master
#4The MR is closed
This is it https://github.com/openjdk/jdk/commit/cc278dbb8a1ca0754d5842...
Re: JEP 401: Value Objects (Preview) merged to OpenJDK master
#5How much of Valhalla is this? 50% of it? 90% of it?
50% maybe.
There are other projects that depend having it in place, SIMD (vectors), reiffed generics, non nullable types.
Re: JEP 401: Value Objects (Preview) merged to OpenJDK master
#6If I understand this correctly then Integer becomes a value class and every instance of it loses its object identity.
I do not have a lot of knowledge about the details but from the outset it seems like a rather bold move to me.
Re: JEP 401: Value Objects (Preview) merged to OpenJDK master
#72934 commits OMG... huge work.
It's a project years in the making.
Re: JEP 401: Value Objects (Preview) merged to OpenJDK master
#8If I understand this correctly then Integer becomes a value class and every instance of it loses its object identity. I do not have a lot of knowledge about the details but from the outset it seems like a rather bold move to me.
Java has a mechanism for Integer and Long objects caching using something that already looks like value object, cached objects can be compared using ==. hashCode of Integer already returns int, the boxed int value. Not much of value is lost.
Re: JEP 401: Value Objects (Preview) merged to OpenJDK master
#9What's the latest status? Is it still limited to 63-bits of data plus 1 bit for nullability?
Re: JEP 401: Value Objects (Preview) merged to OpenJDK master
#10[deleted]