On Wed, 18 Nov 2026 06:55:56 GMT, Markus Grönlund <[email protected]> wrote:

>> Thanks for clarifying the expectation here. I still have a concern though:
>> 
>>> 3. When execution reaches those sites, resolution invokes their bootstrap 
>>> methods again. Newly generated lambda proxy classes are now defined without 
>>> STRONG_LOADER_LINK, because the caller satisfies the redefinition predicate.
>> 
>> So what now ensures the strong link to these temporary proxy classes whilst 
>> tracing is enabled?
>
> The resolved call site already retains the lambda implementation through its 
> target method handle. Removing STRONG_LOADER_LINK leaves those references 
> intact; it removes the additional requirement to retain the class for the 
> lifetime of its defining loader.

Is that specific to this usecase? I'm just wondering where the usual 
requirement to link these to the lifetime of the defining loader comes from, if 
they can't be used once the target method handle becomes unreachable.

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/33921#discussion_r4610268146

Reply via email to