jlink: pre-generate lambda classes

[Brian Goetz]

Is there any mechanical impediment to pushing to an experimental branch 
(e.g., committer status, repo config), or are you just asking about how 
to coordinate work in progress?  If the latter, creating experimental 
branches is fair game, and clear naming and communication is really the 
only requirement.



On 6/26/2023 11:18 AM, Dan Heidinga wrote:
> I've updated my jlink patch to pregenerate lambda classes [0] so it 
> works with the current Leyden repo and the updated classfile api 
> (which is awesome - check it out if you haven't yet!).  Previously 
> discussed in the "Bytecode transformation investigation" thread [1].
>
> I'd like to push it to an experimental branch here on the leyden repo 
> so that others can freely pick up and experiment with the code.  Would 
> that be possible?
>
> My local branch is called "pregenerate-lambdas" but any name would 
> work for me.
>
> The patch pre-generates during jlink time classes for non-Serializable 
> lambda expressions and uses NestMates to handle access to the private 
> implementation method.  It's a good example of the kinds of changes 
> needed to shift runtime-generated classes to jlink time.
>
> Still lots to update but worth getting into Leyden repo so the code is 
> shareable.
>
> Mark / Brian - is it possible to get an experimental branch on the 
> leyden repo for this patch?
>
> --Dan
>
> [0] 
> https://github.com/openjdk/leyden/compare/master...DanHeidinga:leyden:pregenerate-lambdas?expand=1
>
> [1] https://mail.openjdk.org/pipermail/leyden-dev/2022-August/000055.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/leyden-dev/attachments/20230626/512c09c6/attachment.htm>