- Notifications
You must be signed in to change notification settings - Fork3.1k
Companions and nested classes are nestmates#10765
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:2.13.x
Are you sure you want to change the base?
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
som-snytt commentedApr 23, 2024 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
"Just a WIP." The test needs |
9d76195
to724e15a
Comparesom-snytt commentedAug 27, 2024 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
I think I saw that it allowed TopHeavy$Nested host = TopHeavy$ that is, nest host as transitive. I don't see that supported in the spec. I confirmed that the member was private. oh, Edit: the spec says nest mates are not verified on load but by access, so I need to run the (bad) code. Edit again: it already is a run test. Flatten was tweaked so that TopHeavy is the host and lists both classes as members. I won't experiment further. That was on Temurin-22.0.2+9 for future reference. |
It would be nice to have a POC. |
IIUC in this PR you're using nestmates to avoid |
Uh oh!
There was an error while loading.Please reload this page.
Avoid special widened access in ExplicitOuter, compute nestmates in Flatten.
Contingent only on JDK 11 target.