-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8066694: Strange code in JavacParser.java #1852
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
8066694: Strange code in JavacParser.java #1852
Conversation
👋 Welcome back turbanoff! A progress list of the required criteria for merging this PR into |
@turbanoff 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. |
Webrevs
|
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 suspect this was originally a merge issue, in the work leading up to the integration of the JSR308 work.
src/jdk.compiler/share/classes/com/sun/tools/javac/parser/JavacParser.java
Show resolved
Hide resolved
Do you know is history of original changes available somewhere? |
Mailing list message from Jonathan Gibbons on compiler-dev: On 12/22/20 10:52 AM, Andrey Turbanov wrote: It may be available somewhere, but I don't see a need to go there. The -- Jon |
@turbanoff This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
@turbanoff This pull request has been inactive for more than 8 weeks and will now be automatically closed. If you would like to continue working on this pull request in the future, feel free to reopen it! |
Issue is still actual |
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.
LOTM
How to reopen this PR? |
/open |
@lgxbslgx @HostUserDetails{id=13688759, username='lgxbslgx', fullName='null'} only the pull request author can set the pull request state to "open" |
@turbanoff you can type |
/open |
@turbanoff @HostUserDetails{id=741251, username='turbanoff', fullName='null'} this pull request is now open |
@turbanoff 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 1688 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. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@jonathan-gibbons, @JimLaskey, @vicente-romero-oracle, @irisclark) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
@turbanoff |
@turbanoff This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
Just curious, is there anything wrong with this pull request so that no commiter sponsors it after approval? |
/sponsor |
@JimLaskey @turbanoff Since your change was applied there have been 2349 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 36bff6f. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This code was introduced in main repository under https://bugs.openjdk.java.net/browse/JDK-8006775
I checked original commit in
type-annotations/langtools
repository: https://hg.openjdk.java.net/type-annotations/type-annotations/langtools/rev/71f35e4b93a5Looks like it's not a merge problem.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/1852/head:pull/1852
$ git checkout pull/1852
Update a local copy of the PR:
$ git checkout pull/1852
$ git pull https://git.openjdk.java.net/jdk pull/1852/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 1852
View PR using the GUI difftool:
$ git pr show -t 1852
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/1852.diff