Fixed wrong targets for virtual invokes #925
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
Damtev
force-pushed
the
damtev/unsat_type_constraints_253
branch
from
e0fc5bd to
8f818da
Compare
Damtev
changed the title
Damtev
force-pushed
the
damtev/unsat_type_constraints_253
branch
from
8f818da to
aaa514a
Compare
CaelmBleidd
approved these changes
Sep 21, 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
Fixed wrong targets for virtual invokes when we have a user class that implements an interface for that we have predefined library targets.
Fixes #253.
Type of Change
How Has This Been Tested?
Automated Testing
org.utbot.examples.stream.BaseStreamExampleTest#testCustomCollectionStreamExampleChecklist :