Closed
Conversation
0905d71 to
aee86cd
Compare
aee86cd to
bff7df1
Compare
dwijnand
previously approved these changes
Sep 29, 2017
| } | ||
|
|
||
| // sbt/zinc#389: Ignore nulls coming from generic parameter types of lambdas | ||
| private[this] def ignoreNulls[T: scala.reflect.ClassTag](genericTypes: Array[T]): Array[T] = |
ad6638d to
b05a5c9
Compare
Member
Author
|
Things that I need to do before merge:
|
dwijnand
reviewed
Sep 29, 2017
| private[this] def parameterTypes(m: Method): Array[Type] = | ||
| ignoreNulls(m.getGenericParameterTypes) | ||
| private[this] def parameterTypes(c: Constructor[_]): Array[Type] = | ||
| ignoreNulls(c.getGenericParameterTypes) |
Member
There was a problem hiding this comment.
Did the previous iteration of this patch that only applied the filter on getActualTypeArguments fail the test in CI?
Member
Author
There was a problem hiding this comment.
Yes, the issue is that I forgot to push the latest local changes last night, which included this.
Member
Author
|
This slipped through the rocks. Handling tomorrow. |
Member
Author
|
It looks like I cannot sign in into JDK's issue tracker, so I won't be filing a ticket. I'm updating the commit message with the reason behind this problem. |
`Method.getGenericParameterType` may sometimes return `null` for the return types when the method's return type is indeed generic. It's not clear yet where this "sometimes" happens, but it looks like the JDK is not able to tell the return type of a lambda returning the generic class. This can be seen in the `java-lambda-typeparams` scripted test. In this context, lambda metafactory synthesizes a lambda class that returns a class that is parameterized in its return type. In that context, when `ClassToAPI` inspects the synthesized lambda and tries to figure out the full return type of it, the `null` is returned. It looks like the Java reflection API sparingly returns `null`s. We can see that in `ClassToAPI` where we guard against `null`s in lots of other places. So the guard added by this commit is not a novelty, but rather the norm. Fixes sbt#389.
Member
Author
|
This PR has been updated with a better commit message. |
Member
|
So this should target 1.0.x branch, right? |
Member
|
Closing this in favor of #446. |
Member
Author
|
Thanks for the rebase. I missed this notification. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a WIP and needs to be double-checked before merge.
Related but not exact reasons why this happens can be found in JDK's
issue tracker: https://bugs.openjdk.java.net/browse/JDK-8178523?jql=text%20%7E%20%22lambda%20generic%20type%22
We ignore nulls that are returned by
getActualTypeArguments.It would be good to file a ticket in JIRA before merge.
Fixes #389.