-
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
8296846: Minor cleanup of some dead code in Flow.java #11112
Conversation
👋 Welcome back archiecobbs! A progress list of the required criteria for merging this PR into |
@archiecobbs 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. |
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
@archiecobbs 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 72 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 (@vicente-romero-oracle) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
Thanks for the review. /integrate |
@archiecobbs |
/sponsor |
@TheShermanTanker Only Committers are allowed to sponsor changes. |
Guess my committer status promotion hasn't been fully registered with the integration system yet, sorry @archiecobbs |
/sponsor |
Going to push as commit 2f063b8.
Your commit was automatically rebased without conflicts. |
@vicente-romero-oracle @archiecobbs Pushed as commit 2f063b8. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This patch removes two bits of dead code that I ran across.
The only interesting bit is the second patch, which removes this check:
because it's always preceded by this more general check:
and so can never match.
So the patch preserves the existing behavior, but the bit being removed there begs the question: was there some scenario where
tree.sym.flags()
could have bothSYNTHETIC
andLAMBDA_METHOD
that we were supposed to be handling?As it turns out, the
LAMBDA_METHOD
flag is only ever set byLambdaToMethod
, but that class runs after this code (during flow analysis). So if there ever was any such scenario, it can no longer happen anyway.Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/11112/head:pull/11112
$ git checkout pull/11112
Update a local copy of the PR:
$ git checkout pull/11112
$ git pull https://git.openjdk.org/jdk pull/11112/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 11112
View PR using the GUI difftool:
$ git pr show -t 11112
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/11112.diff