-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
8345944: JEP 492: extending local class in a different static context should not be allowed #22679
Conversation
👋 Welcome back mcimadamore! A progress list of the required criteria for merging this PR into |
} | ||
} else if (tree.meth.hasTag(SELECT)) { | ||
log.error(tree.meth.pos(), | ||
Errors.IllegalQualNotIcls(site.tsym)); | ||
attribExpr(((JCFieldAccess) tree.meth).selected, localEnv, site); | ||
} | ||
|
||
if (tree.meth.hasTag(IDENT)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've moved this code outside the if (encl != null)
so that now it can be applied to all kind of superclasses. Note that checkNewInnerClass
will also check whether the target class is either inner or local, so we don't need to check anything else here.
@mcimadamore This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 128 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
@mcimadamore The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
@@ -3065,7 +3070,7 @@ public void report(DiagnosticPosition _unused, JCDiagnostic details) { | |||
} | |||
|
|||
void checkNewInnerClass(DiagnosticPosition pos, Env<AttrContext> env, Type type, boolean isSuper) { | |||
boolean isLocal = type.tsym.owner.kind == MTH; | |||
boolean isLocal = type.tsym.owner.kind == VAR || type.tsym.owner.kind == MTH; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Most local classes will have their owner set to some method symbols. But, in some corner cases where a local class is defined inside a field initializer, the owner can actually be a variable symbol too.
@@ -3834,7 +3834,7 @@ Symbol findSelfContaining(DiagnosticPosition pos, | |||
*/ | |||
Symbol findLocalClassOwner(Env<AttrContext> env, TypeSymbol c) { | |||
Symbol owner = c.owner; | |||
Assert.check(owner.kind == MTH); | |||
Assert.check(owner.kind == MTH || owner.kind == VAR); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We now need to generalize this, so that it works for both method and variable owners.
/solves 8345953 |
@mcimadamore |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
/integrate |
Going to push as commit 0ad6423.
Your commit was automatically rebased without conflicts. |
@mcimadamore Pushed as commit 0ad6423. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
/backport :jdk24 |
@mcimadamore The target repository There is a branch |
/backport :jdk24 |
@mcimadamore the backport was successfully created on the branch backport-mcimadamore-0ad64234-jdk24 in my personal fork of openjdk/jdk. To create a pull request with this backport targeting openjdk/jdk:jdk24, just click the following link: The title of the pull request is automatically filled in correctly and below you find a suggestion for the pull request body:
If you need to update the source branch of the pull then run the following commands in a local clone of your personal fork of openjdk/jdk:
|
This PR fixes a couple of issues associated with the implementation of the new stricter checks for local class creation defined by JEP 492.
There are two issues:
Progress
Issues
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/22679/head:pull/22679
$ git checkout pull/22679
Update a local copy of the PR:
$ git checkout pull/22679
$ git pull https://git.openjdk.org/jdk.git pull/22679/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 22679
View PR using the GUI difftool:
$ git pr show -t 22679
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/22679.diff
Using Webrev
Link to Webrev Comment