-
Notifications
You must be signed in to change notification settings - Fork 38.5k
ResolvableType should support resolving lambda types [SPR-13698] #18273
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
Comments
Stéphane Nicoll commented I thought we had already such report (with a lengthy discussion with thomas.darimont) but I can't find it anymore |
Juergen Hoeller commented Indeed, we rejected in back then since the "API introduced in Java 8" is actually internal ( Juergen |
Oliver Drotbohm commented Maybe we should bring this up with the JDK team then, they might be able to fix this? I haven't looked deeply into the code but is there a particular reason the standard lookup algorithm doesn't work here? I just think it's kind of weird to see a lambda failing while the very same declaration works if you create the anonymous class. It basically subverts our "use Java 8 and everything will be better" message to some degree. |
Oliver Drotbohm commented I just ran into this again with code that was expecting a |
Oliver Drotbohm commented For reference, here's the discussion I had with the JDK team: http://mail.openjdk.java.net/pipermail/compiler-dev/2016-December/010623.html |
Bulk closing outdated, unresolved issues. Please, reopen if still relevant. |
Uh oh!
There was an error while loading. Please reload this page.
Oliver Drotbohm opened SPR-13698 and commented
This test case currently fails:
This helper library (itself inspired by Spring's GenericTypeResolver) seems to use an additional code path to use API introduced in Java 8 to resolve lambdas in a special way.
Issue Links:
The text was updated successfully, but these errors were encountered: