Skip to content

Correct input initialization in builtin function #2935

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 13, 2018

Conversation

romainbrenguier
Copy link
Contributor

Result was moved twice instead of initializing input field with the
given input.

Result was moved twice instead of initializing `input` field with the
given `input`.
Copy link
Member

@peterschrammel peterschrammel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a regression test for this?

Copy link
Contributor

@mgudemann mgudemann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mgudemann
Copy link
Contributor

@peterschrammel this fixes what makes TG regression test fail atm
@romainbrenguier a TG bump would be good!

Copy link
Contributor

@allredj allredj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Passed Diffblue compatibility checks (cbmc commit: 7857669).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/84531511

@peterschrammel
Copy link
Member

@romainbrenguier, can we close this (since it's now part of #2917)?

@mgudemann mgudemann merged commit 7857669 into develop Sep 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants