Draft JEP Announcement: "Computed Constants"

[Maurizio Cimadamore]

Hi Remi
Yes, of course we were aware of that.

Think of this proposal as an API-driven approach (in the style of 
ThreadLocal, ClassValue, ScopedValue, ...) which delivers more or less 
the same feature, but w/o changing the language.


One thing that's attractive about the API approach is that it is not 
limited to just static fields, but it can also work for instance fields 
as well.


(that said, I agree the two jeps should somehow be related/link to each 
other)


Maurizio


On 27/07/2023 17:09, Remi Forax wrote:
> Hello,
> Are you aware of the lazy static final fields proposal ?
> https://bugs.openjdk.org/browse/JDK-8209964
>
> In think both proposals should be merged.
>
> Rémi
>
> ------------------------------------------------------------------------
>
>     *From: *"Per-Ake Minborg" <per-ake.minborg at oracle.com>
>     *To: *"leyden-dev" <leyden-dev at openjdk.org>
>     *Sent: *Thursday, July 27, 2023 5:52:46 PM
>     *Subject: *Draft JEP Announcement: "Computed Constants"
>
>     Hi all,
>
>       Maurizio and I have drafted a JEP for computed constants, which are
>       immutable value holders that are initialized at most once.  They
>     offer
>       the performance and safety benefits of final fields while offering
>       greater flexibility as to the timing of initialization.  In the
>       context of Leyden, they could be one basis for shifting computation
>       both forward and backward in time.
>
>       The draft is here:https://openjdk.org/jeps/8312611
>     <https://openjdk.org/jeps/8312611>
>
>       Now that the Leyden repo is open, I’ll publish the prototype
>     code to a
>       new branch there shortly.
>
>       Comments are welcome!
>
>       Best, Per
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/leyden-dev/attachments/20230727/65f02f0f/attachment.htm>