> After the ClassFile API migration, when serializable lambdas are requested
> for hidden class callers, illegal class name is generated for the
> serialization methods, which previously had legal yet unusable class names,
> as hidden classes cannot be described by a `CONSTANT_Class_info`.
>
>
On Wed, 13 Nov 2024 17:01:14 GMT, Chen Liang wrote:
>> After the ClassFile API migration, when serializable lambdas are requested
>> for hidden class callers, illegal class name is generated for the
>> serialization methods, which previously had legal yet unusable class names,
>> as hidden cla
On Wed, 13 Nov 2024 18:30:22 GMT, Chen Liang wrote:
>> After the ClassFile API migration, when serializable lambdas are requested
>> for hidden class callers, illegal class name is generated for the
>> serialization methods, which previously had legal yet unusable class names,
>> as hidden cla
> After the ClassFile API migration, when serializable lambdas are requested
> for hidden class callers, illegal class name is generated for the
> serialization methods, which previously had legal yet unusable class names,
> as hidden classes cannot be described by a `CONSTANT_Class_info`.
>
>
On Wed, 13 Nov 2024 09:10:57 GMT, Jorn Vernee wrote:
>> Re this sentence: I wish to indicate "caller is unloaded and impl class is
>> unreachable elsewhere (besides in the ClassLoader)". Maybe just "caller is
>> unloaded" is fine. Thoughts on phrasing?
>
> Maybe 'caller's class is unloaded'.
>
On Wed, 13 Nov 2024 00:01:40 GMT, Chen Liang wrote:
>> src/java.base/share/classes/java/lang/invoke/LambdaMetafactory.java line 244:
>>
>>> 242: * implementation class from unloading when the caller is a {@linkplain
>>> 243: * MethodHandles.Lookup.ClassOption#STRONG hidden class} and is
>>> u
On Tue, 12 Nov 2024 18:00:01 GMT, Chen Liang wrote:
>> After the ClassFile API migration, when serializable lambdas are requested
>> for hidden class callers, illegal class name is generated for the
>> serialization methods, which previously had legal yet unusable class names,
>> as hidden cla
On Tue, 12 Nov 2024 23:13:16 GMT, Jorn Vernee wrote:
>> Chen Liang has updated the pull request with a new target base due to a
>> merge or a rebase. The incremental webrev excludes the unrelated changes
>> brought in by the merge/rebase. The pull request contains six additional
>> commits sin
On Tue, 5 Nov 2024 19:21:58 GMT, Chen Liang wrote:
>> After the ClassFile API migration, when serializable lambdas are requested
>> for hidden class callers, illegal class name is generated for the
>> serialization methods, which previously had legal yet unusable class names,
>> as hidden clas
> After the ClassFile API migration, when serializable lambdas are requested
> for hidden class callers, illegal class name is generated for the
> serialization methods, which previously had legal yet unusable class names,
> as hidden classes cannot be described by a `CONSTANT_Class_info`.
>
>
On Tue, 5 Nov 2024 19:21:58 GMT, Chen Liang wrote:
>> After the ClassFile API migration, when serializable lambdas are requested
>> for hidden class callers, illegal class name is generated for the
>> serialization methods, which previously had legal yet unusable class names,
>> as hidden clas
> After the ClassFile API migration, when serializable lambdas are requested
> for hidden class callers, illegal class name is generated for the
> serialization methods, which previously had legal yet unusable class names,
> as hidden classes cannot be described by a `CONSTANT_Class_info`.
>
>
On Tue, 5 Nov 2024 18:29:52 GMT, Chen Liang wrote:
> After the ClassFile API migration, when serializable lambdas are requested
> for hidden class callers, illegal class name is generated for the
> serialization methods, which previously had legal yet unusable class names,
> as hidden classes
On Tue, 5 Nov 2024 18:29:52 GMT, Chen Liang wrote:
> After the ClassFile API migration, when serializable lambdas are requested
> for hidden class callers, illegal class name is generated for the
> serialization methods, which previously had legal yet unusable class names,
> as hidden classes
On Tue, 5 Nov 2024 18:29:52 GMT, Chen Liang wrote:
> After the ClassFile API migration, when serializable lambdas are requested
> for hidden class callers, illegal class name is generated for the
> serialization methods, which previously had legal yet unusable class names,
> as hidden classes
After the ClassFile API migration, when serializable lambdas are requested for
hidden class callers, illegal class name is generated for the serialization
methods, which previously had legal yet unusable class names, as hidden classes
cannot be described by a `CONSTANT_Class_info`.
This patch r
16 matches
Mail list logo
