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
8244711: [lworld] Javac needs to tweak checks for interface implementation by an inline type. #41
Conversation
|
@sadayapalam This change now passes all automated pre-integration checks, type
There are currently no new commits on the
|
Webrevs
|
Since asSuper is always called with a true checkReferenceProjection, why not drop the argument and rename as asSuperWithProjection (or some such). If you introduce a need later for the false case then you can just call asSuper directly. I.E., argument seems redundant.
test/langtools/tools/javac/valhalla/lworld-values/AutoCloseableTest.java
Outdated
Show resolved
Hide resolved
test/langtools/tools/javac/valhalla/lworld-values/ConflictingSuperInterfaceTest.java
Outdated
Show resolved
Hide resolved
test/langtools/tools/javac/valhalla/lworld-values/ConflictingSuperInterfaceTest.java
Show resolved
Hide resolved
I agree this looks strange. But rather than asSuperWithProjection, I have reworked it along the lines of existing variants (isSubtype and friends) by making the original asSuper to be a three argument one and all existing calls to the two args asSuper to be routed to the three arg full bodied asSuper with a 3rd argument value of false. |
/integrate |
@sadayapalam |
When javac needs to check if a class implements a particular interface, it should
check if the reference projection of the class is a subtype of the interface. (Rather
than checking if the concerned class is a subtype of the interface)
Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/valhalla pull/41/head:pull/41
$ git checkout pull/41