-
Notifications
You must be signed in to change notification settings - Fork 227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
java.lang.invoke classes left in constant pool #61
Comments
Here is a workaround I'm using to post-process the output. It strips inner classes of types in java.lang.invoke. This is too heavy-handed for the general case, but for my purposes I'm targeting platforms that don't have java.lang.invoke so I can make assumptions that any references to them should be gone.
|
This is fixed in Retrolambda 2.0.4 |
Thanks! On Wed, Jul 8, 2015 at 10:23 AM, Esko Luontola notifications@github.com
Steve Hannah |
After running retrolambda on a class, the constant pool still retains class constants for java.lang.invoke classes (e.g. MethodHandles.Lookup).
Here is the output of java -p on such a class.
Here is the retrolambda command used to generate this:
The text was updated successfully, but these errors were encountered: