Skip to content

[move-function-value] Improve support for uses that are due to binding a moved value to a different value. #58470

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

Conversation

gottesmm
Copy link
Contributor

Most of the tests that I wrote used full on non-consuming/consuming uses rather
than initialization of a variable. This commit fixes that hole in the model and
adds some tests that exercise this behavior. Address moves did not have this
problem due to different codegen.

…g a moved value to a different value.

Most of the tests that I wrote used full on non-consuming/consuming uses rather
than initialization of a variable. This commit fixes that hole in the model and
adds some tests that exercise this behavior. Address moves did not have this
problem due to different codegen.
@gottesmm
Copy link
Contributor Author

@swift-ci test

@gottesmm gottesmm merged commit b38ee6b into swiftlang:main Apr 28, 2022
@gottesmm gottesmm deleted the pr-d1a35ed4ecb18900b41fc392e54ff684267f7753 branch April 28, 2022 06:49
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.

1 participant