fix: Make lambda type implicit to avoid auto-importing type targeted in lambda #4093
Conversation
This file contains 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
|
Clean and green, LGTM. |
slarse
changed the title
|
@monperrus let's merge then, seems like a reasonable enough solution. I've double-checked and there's no way to explicitly specify return type of a lambda expression (which makes sense as lambdas can only target functional interfaces, where the type is already known). |
slarse
changed the title
monperrus
changed the title
|
Thanks for the fix @slarse |
slarse
deleted the
issue/4079-avoid-auto-importing-functional-interface
branch
Merged
woutersmeenk
pushed a commit
to woutersmeenk/spoon
that referenced
this pull request
Aug 29, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix #4079
See #4079 for a description of the problem.