Hacker News Reader

There were another JEP draft [1] recently that was proposing to introduce a lazy keyword for static fields. This new JEP looks like an alternative without any language change, and seems more likely to prevail.

[1] JEP draft: Lazy Static Final Fields - https://openjdk.org/jeps/8209964

Not quite. You need to have control over the JVM to do what this class does. The whole point of this class is a lazy value that interacts with the JIT in desirable ways.

Sure, but that's an (important) implementation detail. If this JEP is merged both Scala and Kotlin could implement their respective features in terms of ComputedConstant and get the performance enhancements for free.

Meaning it's semantically the same, with non-functional benefits.

It also seems very similar to .NET's Lazy<T>: https://learn.microsoft.com/en-us/dotnet/api/system.lazy-1?v...