Correct input initialization in builtin function#2935
Merged
Conversation
Result was moved twice instead of initializing `input` field with the given `input`.
Member
peterschrammel
left a comment
There was a problem hiding this comment.
Is there a regression test for this?
Contributor
|
@peterschrammel this fixes what makes TG regression test fail atm |
allredj
reviewed
Sep 12, 2018
Contributor
allredj
left a comment
There was a problem hiding this comment.
Passed Diffblue compatibility checks (cbmc commit: 7857669).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/84531511
This was referenced Sep 12, 2018
Member
|
@romainbrenguier, can we close this (since it's now part of #2917)? |
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
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.
Result was moved twice instead of initializing
inputfield with thegiven
input.