Skip to content

[ownership] Change ReturnInst to have its ValueOwnershipKind stored within it rather than always recomputing from the function type. #34644

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

@gottesmm gottesmm commented Nov 9, 2020

This allows us to hoist the error case of having a function signature with
conflicting ownership requirements into the creation of the return inst instead
of at the time of computing Operand Constraints.

This is the last part of the Operand Constraint computation that can fail that
once removed will let me use fail to mean any constriant is allowed.

…ithin it rather than always recomputing from the function type.

This allows us to hoist the error case of having a function signature with
conflicting ownership requirements into the creation of the return inst instead
of at the time of computing Operand Constraints.

This is the last part of the Operand Constraint computation that can fail that
once removed will let me use fail to mean any constriant is allowed.
@gottesmm gottesmm requested review from atrick and meg-gupta November 9, 2020 22:21
@gottesmm
Copy link
Contributor Author

gottesmm commented Nov 9, 2020

@swift-ci smoke test

@gottesmm
Copy link
Contributor Author

@swift-ci smoke test OS X platform

@gottesmm gottesmm merged commit a0cb311 into swiftlang:main Nov 10, 2020
@gottesmm gottesmm deleted the pr-e398af60dfa740b58a743d92dc2fdc617e9c9bf0 branch November 10, 2020 02:35
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