Skip to content

[Foundation][runtime] Remove swift_errorBridgingInfo #28685

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

lorentey
Copy link
Member

@lorentey lorentey commented Dec 10, 2019

To implement swift_errorBridgingInfo, the Foundation overlay needs to import private runtime headers. Now that we cannot statically link the Foundation overlay, there is no point to keeping this workaround in the overlay. Remove it and let the runtime individually dlsym these things when it needs them.

This is more or less a revert of #16677.

rdar://problem/57809306

To implement swift_errorBridgingInfo, the Foundation overlay needs to import private runtime headers. Now that we cannot statically link the Foundation overlay, there is no point to keeping this workaround in the overlay any more.

This effectively reverts swiftlang#16677.

rdar://problem/57809306
@lorentey
Copy link
Member Author

@swift-ci test

@lorentey lorentey requested a review from mikeash December 10, 2019 23:34
Copy link
Contributor

@mikeash mikeash left a comment

Choose a reason for hiding this comment

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

Looks good! According to what I wrote on that previous PR, this technique was problematic when statically linking the Swift libraries. We don't support that anymore so that's no longer an issue.

@lorentey lorentey merged commit 4c3c335 into swiftlang:master Dec 11, 2019
@lorentey lorentey deleted the i-heard-you-like-runtime-so-i-put-a-runtime-in-your-foundation-overlay-so-you-can-run-while-you-found branch December 11, 2019 18:54
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.

2 participants