Skip to content

[stdlib] Fix availability of Dictionary’s bulk-loading initializer #23643

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
Mar 29, 2019

Conversation

lorentey
Copy link
Member

These entry points were introduced in #21235. Adding @_alwaysEmitIntoClient makes them available in all OS versions.

rdar://problem/49404177

Making it @_alwaysEmitIntoClient makes it available in all OS versions.
@lorentey lorentey requested a review from Catfish-Man March 29, 2019 00:50
@lorentey
Copy link
Member Author

@swift-ci smoke test

@lorentey lorentey merged commit 7b654b3 into swiftlang:master Mar 29, 2019
@lorentey lorentey deleted the bulk-emissions branch March 29, 2019 19:55
lorentey added a commit to lorentey/swift that referenced this pull request Apr 3, 2019
The initializer was originally introduced without proper availability; in swiftlang#23643, we fixed this by applying the `@_alwaysEmitIntoClient` attribute. However, this had the unfortunate side-effect that the symbol disappeared from `libswiftCore.dylib`, which somehow confuses some simulator builds.

Try to figure out what’s happening by replacing the third closure argument with an integer return value. This changes the mangled name of the bulk initializer, which should make it more obvious how/why these builds fail.

rdar://problem/49479386
lorentey added a commit to lorentey/swift that referenced this pull request Apr 3, 2019
The initializer was originally introduced without proper availability; in swiftlang#23643, we fixed this by applying the `@_alwaysEmitIntoClient` attribute. However, this had the unfortunate side-effect that the symbol disappeared from `libswiftCore.dylib`, which somehow confuses some simulator builds.

Try to figure out what’s happening by replacing the third closure argument with an integer return value. This changes the mangled name of the bulk initializer, which should make it more obvious how/why these builds fail.

rdar://problem/49479386
(cherry picked from commit e72e328)
lorentey added a commit that referenced this pull request Apr 3, 2019
The initializer was originally introduced without proper availability; in #23643, we fixed this by applying the `@_alwaysEmitIntoClient` attribute. However, this had the unfortunate side-effect that the symbol disappeared from `libswiftCore.dylib`, which somehow confuses some simulator builds.

Try to figure out what’s happening by replacing the third closure argument with an integer return value. This changes the mangled name of the bulk initializer, which should make it more obvious how/why these builds fail.

rdar://problem/49479386
lorentey added a commit that referenced this pull request Apr 3, 2019
The initializer was originally introduced without proper availability; in #23643, we fixed this by applying the `@_alwaysEmitIntoClient` attribute. However, this had the unfortunate side-effect that the symbol disappeared from `libswiftCore.dylib`, which somehow confuses some simulator builds.

Try to figure out what’s happening by replacing the third closure argument with an integer return value. This changes the mangled name of the bulk initializer, which should make it more obvious how/why these builds fail.

rdar://problem/49479386
(cherry picked from commit e72e328)
millenomi pushed a commit to swiftlang/swift-corelibs-foundation that referenced this pull request Nov 11, 2020
The initializer was originally introduced without proper availability; in swiftlang/swift#23643, we fixed this by applying the `@_alwaysEmitIntoClient` attribute. However, this had the unfortunate side-effect that the symbol disappeared from `libswiftCore.dylib`, which somehow confuses some simulator builds.

Try to figure out what’s happening by replacing the third closure argument with an integer return value. This changes the mangled name of the bulk initializer, which should make it more obvious how/why these builds fail.

rdar://problem/49479386
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