Since LMF goes through Lookup::defineHiddenClass, does this mean that
they will be potentially dumped twice, once through Lookup, and once
through LMF?
Now that there is a shared implementation, perhaps we should migrate use
in LMF to something more like
-Djava.lang.invoke.MethodHandle.DU
> This implements a shared utility to dump generated classes defined as
> normal/hidden classes via `Lookup` API. This replaces the implementation in
> `LambdaMetaFactory` and method handle implementation that dumps the hidden
> class bytes on disk for debugging.
>
> For classes defined vi
On Fri, 24 Mar 2023 20:54:25 GMT, Chen Liang wrote:
>> Mandy Chung has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> avoid another map lookup
>
> src/java.base/share/classes/java/lang/invoke/ClassFileDumper.java line 88:
>
>> 86:
On Fri, 24 Mar 2023 20:41:41 GMT, Mandy Chung wrote:
> This implements a shared utility to dump generated classes defined as
> normal/hidden classes via `Lookup` API. This replaces the implementation in
> `LambdaMetaFactory` and method handle implementation that dumps the hidden
> class byte
This implements a shared utility to dump generated classes defined as
normal/hidden classes via `Lookup` API. This replaces the implementation in
`LambdaMetaFactory` and method handle implementation that dumps the hidden
class bytes on disk for debugging.
For classes defined via `Lookup::d
