-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8347530: Improve error message with invalid permits clauses #25255
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
base: master
Are you sure you want to change the base?
Conversation
👋 Welcome back abimpoudis! A progress list of the required criteria for merging this PR into |
@biboudis 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 19 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 |
Webrevs
|
@@ -5471,8 +5471,19 @@ void attribClass(ClassSymbol c) throws CompletionFailure { | |||
.stream() | |||
.anyMatch(d -> d.tsym == c); | |||
if (!thisIsASuper) { | |||
log.error(TreeInfo.diagnosticPositionFor(subType.tsym, env.tree), | |||
Errors.InvalidPermitsClause(Fragments.DoesntExtendSealed(subType))); | |||
KindName subtypingLeftKind; |
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 wonder, would: KindName.kindName(subType.tsym)
work?
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.
Indeed and I updated the PR. Thanks @lahodaj
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.
Looks good to me!
Currently we report one kind of error message (
subclass {0} must extend sealed class
) when there is a compile-type error in cases like the following:This PR proposes to improve error reporting since there are other kinds of declarations that can also participate in sealed hierarchies like records, enums and interfaces.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/25255/head:pull/25255
$ git checkout pull/25255
Update a local copy of the PR:
$ git checkout pull/25255
$ git pull https://git.openjdk.org/jdk.git pull/25255/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 25255
View PR using the GUI difftool:
$ git pr show -t 25255
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/25255.diff
Using Webrev
Link to Webrev Comment