Disabled concrete execution for lambda results #989
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
… as method result
Damtev
force-pushed
the
damtev/disable_concrete_lambda_results
branch
from
020247b to
9580b14
Compare
sergeypospelov
approved these changes
Sep 22, 2022
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.
Description
As lambda value could not be converted to
UtLambdaModel, we cannot use concrete execution when we method result is lambda. So, this PR disables the concrete execution forUtLambdaModelresults.Fixes #192, fixes #958.
Type of Change
Bug fix (non-breaking change which fixes an issue)
How Has This Been Tested?
Automated Testing
org.utbot.examples.lambda.SimpleLambdaExamplesTest#testChoosePredicateChecklist (remove irrelevant options):