[embedded] Make stdlib APIs automatically available on older Darwin versions in Embedded Swift #78263
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kubamracek
requested review from
MaxDesiatov,
jckarter,
phausler,
rauhul,
zoecarver,
eeckstein and
tshortli
tshortli
reviewed
Dec 18, 2024
…ersions in Embedded Swift
kubamracek
force-pushed
the
embedded-stdlib-all-available
branch
from
6ff0c8e to
2446923
Compare
|
@swift-ci please test |
tshortli
approved these changes
Dec 18, 2024
|
@swift-ci please test |
kubamracek
force-pushed
the
embedded-stdlib-all-available
branch
from
008ff04 to
0545277
Compare
|
@swift-ci please test |
|
@swift-ci please test Linux platform |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The motivation here is about using types and API that have been recently added to the stdlib with an availability only in a recent macOS release (for regular Swift) because the stdlib ships as part of the OS. However, we don't have that constraint with Embedded Swift where the stdlib/runtime is statically included into the produced binaries, and therefore we should be able to use such stdlib types regardless of the "official" availability for regular Swift.