-
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
8273257: jshell doesn't compile a sealed hierarchy with a sealed interface and a non-sealed leaf #5348
Conversation
…face and a non-sealed leaf
👋 Welcome back jlahoda! A progress list of the required criteria for merging this PR into |
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
@lahodaj 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 239 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 |
/integrate |
Going to push as commit 7b023a3.
Your commit was automatically rebased without conflicts. |
Considering code like:
javac will currently produce these compile-time errors:
The second error confuses JShell in cases like:
Because when compiling the second snippet, JShell needs to analyze both these snippets together, but the second error seems unrepairable to JShell, so it does not try to include the first snippet in the compilation.
While JShell could be changed to consider the second error repairable, it seems better to tweak the error recovery to skip the second error, as javac does not know whether the
Undefined
interface is or is not sealed.There is already code attempting to skip the error for erroneous supertypes, but erroneous superinterfaces are not returned by
Types.directSupertypes
, so attempting to detect cases where superinterfaces are erroneous.Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/5348/head:pull/5348
$ git checkout pull/5348
Update a local copy of the PR:
$ git checkout pull/5348
$ git pull https://git.openjdk.java.net/jdk pull/5348/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 5348
View PR using the GUI difftool:
$ git pr show -t 5348
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/5348.diff