<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<font size="4"><font face="monospace">Since LMF goes through
Lookup::defineHiddenClass, does this mean that they will be
potentially dumped twice, once through Lookup, and once through
LMF? <br>
<br>
Now that there is a shared implementation, perhaps we should
migrate use in LMF to something more like</font></font>
<pre class="moz-quote-pre" wrap=""> -Djava.lang.invoke.MethodHandle.DUMP_LAMBDA_PROXY_CLASS_FILES=true</pre>
<font size="4"><font face="monospace">and retire the separate
dumpProxyClasses flag.<br>
</font></font><br>
<div class="moz-cite-prefix">On 3/24/2023 4:49 PM, Mandy Chung
wrote:<br>
</div>
<blockquote type="cite" cite="mid:lLamM86s9WeIZf1DFeIwo3Sz9ZykSggaQm_Y6tNs3Ng=.a3be4ab9-b8ae-4bf0-94a4-eee798b65dc0@github.com">
<pre class="moz-quote-pre" wrap="">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.</pre>
</blockquote>
<br>
</body>
</html>