Fix compilation of tests on older macOS #385
Merged
Conversation
This file contains 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
czechboy0
approved these changes
Nov 17, 2023
|
Whoops, thanks |
simonjbeaumont
force-pushed
the
sb/fix-compilation-on-macOS-12
branch
from
be8d0e2
to
b143565
Compare
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.
Motivation
The tests fail to compile on anything older than macOS 13, because they use
Collection.split(separator:maxSplits:omittingEmptySubsequences:), which is only available in macOS 13+.Modifications
Rather than use
->in the stringified tests, use just>, which means the function resolves toString.split(separator:maxSplits:omittingEmptySubsequences:), which is available on older platforms.Result
Tests can be built on older platforms.
Test Plan
Manual verification.