Nope not at all, here you go: https://openjdk.org/jeps/401 https://openjdk.org/jeps/401 It's part of Valhalla, as a pre-requirement for heap-flattening. Ctrl

Nope not at all, here you go: https://openjdk.org/jeps/401 https://openjdk.org/jeps/401 It's part of Valhalla, as a pre-requirement for heap-flattening. Ctrl+F for "Null-restricted type". The strawman proposal syntax is "Foo!". When inlined, a null-restricted class type should have a heap storage footprint and execution time (when fully optimized) comparable to the primitive types. For example, a Point!, given the class declaration above, can be expected to directly occupy 128 bits in fields and array components, and to avoid any allocation in stack computations. A field access simply references the first or second 64 bits. There are no additional pointers. For a summary of current status and what it means for you as a developer, I recommend the linked email here and the author's comments in the thread: https://www.reddit.com/r/java/comments/13xtog3/valhallas_latest_plans_very_highlevel_accessible/ https://www.reddit.com/r/java/comments/13xtog3/valhallas_lat...