-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8328316: Finisher cannot emit if stream is sequential and integrator returned false #18351
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 vklang! A progress list of the required criteria for merging this PR into |
Just a note to self, consider if this should get backported to 22 or not. |
@viktorklang-ora 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 48 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 |
@viktorklang-ora 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. |
@PaulSandoz Would you mind reviewing this PR, Paul? |
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, just a minor suggestion.
189ffaa
to
8974d9f
Compare
@viktorklang-ora Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information. |
Co-authored-by: Paul Sandoz <paul.d.sandoz@googlemail.com>
/integrate |
Going to push as commit ab28045.
Your commit was automatically rebased without conflicts. |
@viktorklang-ora Pushed as commit ab28045. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Have you decided whether this will be backported to 22? |
/backport jdk22u |
@viktorklang-ora the backport was successfully created on the branch backport-viktorklang-ora-ab28045d in my personal fork of openjdk/jdk22u. To create a pull request with this backport targeting openjdk/jdk22u:master, just click the following link: The title of the pull request is automatically filled in correctly and below you find a suggestion for the pull request body:
If you need to update the source branch of the pull then run the following commands in a local clone of your personal fork of openjdk/jdk22u:
|
Adds differentiation between direct and transitive short circuiting which could prevent pushing downstream in the finisher for built-ins that were not
collect()
.Creating this as a draft PR for now, just need to run some benchmarks to validate no significant regressions first.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/18351/head:pull/18351
$ git checkout pull/18351
Update a local copy of the PR:
$ git checkout pull/18351
$ git pull https://git.openjdk.org/jdk.git pull/18351/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 18351
View PR using the GUI difftool:
$ git pr show -t 18351
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/18351.diff
Webrev
Link to Webrev Comment