Skip to content

[6.1][IRGen] Indirectly pass typed errors for closures with indirect results #78273

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
Dec 20, 2024

Conversation

drexin
Copy link
Contributor

@drexin drexin commented Dec 18, 2024

  • Explanation: In partial application forwarder emission, we were missing a check for indirect results. When results are being returned indirectly, we have to return the error indirectly as well.
  • Scope: Typed throws ABI
  • Issues: rdar://141575655
  • Original PRs: [IRGen] Indirectly pass typed errors for closures with indirect results #78261
  • Risk: Low. Adjusts the code gen behavior to match other cases.
  • Testing: Added regression tests for both cases. Ensured they failed before the fix.
  • Reviewers: @aschwaighofer

rdar://141575655

In partial application forwarder emission, we were missing a check for indirect results.
When results are being returned indirectly, we have to return the error indirectly as well.
@drexin drexin added 🍒 release cherry pick Flag: Release branch cherry picks swift 6.1 labels Dec 18, 2024
@drexin drexin requested a review from a team as a code owner December 18, 2024 18:46
@drexin
Copy link
Contributor Author

drexin commented Dec 18, 2024

@swift-ci test

@drexin
Copy link
Contributor Author

drexin commented Dec 18, 2024

cc: @tbkka

@drexin drexin merged commit 99a9d61 into swiftlang:release/6.1 Dec 20, 2024
5 checks passed
@drexin drexin deleted the wip-141575655-6.1 branch December 20, 2024 01:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🍒 release cherry pick Flag: Release branch cherry picks swift 6.1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants