Skip to content

[5.9] MoveOnlyChecker: Look through convert_function of nonescaping closures. #66823

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

Conversation

jckarter
Copy link
Contributor

Issue: rdar://111060678
• Explanation: Certain uses of nonescaping closures that capture noncopyable values as arguments to a generic function call would cause the compiler to incorrectly raise an error about unknown use of the noncopyable value.
• Scope of Issue: Reject-valid bug.
• Origination: Noncopyable types feature work.
• Risk: Low -- Change only affects new code adopting noncopyable types. The fix is a one-liner filling in an unhandled SIL instruction in the move-only checker.
• Reviewed By: @gottesmm
• Automated Testing: Swift CI
• Dependencies: None
• Builder Impact: Not applicable
• Directions for QE: None

…res.

Like a nested partial_apply reabstraction, but without the thunk, these change
the representation of the function but can't escape it without breaking the
nonescaping closure promotion. rdar://111060678
@jckarter jckarter requested a review from a team as a code owner June 21, 2023 19:27
@jckarter
Copy link
Contributor Author

@swift-ci Please test

@jckarter jckarter merged commit b20f3c4 into swiftlang:release/5.9 Jun 22, 2023
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.

3 participants