-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
8316470: Incorrect error location for "invalid permits clause" depending on file order #16221
Conversation
…ing on file order
👋 Welcome back jlahoda! A progress list of the required criteria for merging this PR into |
JavaFileObject prev = log.useSource(c.sourcefile); | ||
ResultInfo prevReturnRes = env.info.returnResult; | ||
|
||
try { |
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.
Previously this try
block didn't include this code. Is, the new position of try
, intentional?
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 486 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 bf1a14e.
Your commit was automatically rebased without conflicts. |
Consider code like (in two different files, but accessible through source path):
and a javac process that will start attribution with
Main
. As part ofMain
attribution, its superclasses will be attributed, henceC
will be attributed. And there will be a sealing error reported forC
(missing permitted). But, the source in the logger will still be set toMain
, and hence the report will be reported at a weird place inMain
, not inC
.The proposed solution is simple: move the code to set the source to logger (and related code) before the sealed checks. The diff looks scary, but it is movement of several lines up, and whitespace changes.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/16221/head:pull/16221
$ git checkout pull/16221
Update a local copy of the PR:
$ git checkout pull/16221
$ git pull https://git.openjdk.org/jdk.git pull/16221/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 16221
View PR using the GUI difftool:
$ git pr show -t 16221
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/16221.diff
Webrev
Link to Webrev Comment