-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8259025: Record compact constructor using Objects.requireNonNull #1917
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
Conversation
👋 Welcome back lgxbslgx! 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.
Looks good, thanks for fixing this!
@lgxbslgx 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 103 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 (@szegedi) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
/sponsor |
@szegedi @lgxbslgx Since your change was applied there have been 115 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 33fbc10. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Hi all,
Currently, the method
Attr::lambdaEnv
doesn't set thelambdaEnv.info.isLambda
totrue
and lets the caller set it. But not all the callers remember to set it. In this bug,DefferredAttr::attribSpeculativeLambda
usesAttr::lambdaEnv
and doesn't setlambdaEnv.info.isLambda
totrue
. So whenAttr::visitReturn
uses!env.info.isLambda
to judge if it is in the lambda environment, it gets the wrong information and generates an error message.This patch moves
lambdaEnv.info.isLambda = true;
intoAttr::lambdaEnv
to solve the problem and adds a corresponding test case. Thank you for taking the time to review.Best Regards.
Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/1917/head:pull/1917
$ git checkout pull/1917