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.DUMP_LAMBDA_PROXY_CLASS_FILES=true
and retire the separate dumpProxyClasses flag.
On 3/24/2023 4:49 PM, Mandy Chung wrote:
For classes defined via `Lookup::defineClass`, `Lookup::defineHiddenClass` and
`Lookup::defineHiddenClassWithClassData`, by default they will be dumped to the path
specified in `-Djava.lang.invoke.Lookup.dumpClasses=<dumpDir>`
The hidden classes generated for lambdas, `LambdaForms` and method handle
implementation use non-default dumper so that they can be controlled via a
separate system property and path as in the current implementation.
