fix: omit parentheses around lambda body assignment expressions#951
Merged
jtkiesel merged 1 commit intoJun 25, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed with this PR:
Lambda expression bodies that are assignment expressions are no longer wrapped in parentheses. Apparently doing so can cause the Java compiler to consider the lambda as strictly having a return value (so the lambda can no longer be used as a
Consumer, for example), even though assignments always evaluate to a value, and without parentheses they can be used as the body of lambdas with or without a return value. This resolves the issue described in #921 (comment).Example
Input
Output