[NOMERGE] Build the standard library in Swift 4 mode #10981
Closed
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
added 2 commits
July 14, 2017 17:54
This is not ready for merge yet because, at the very least, we don't (yet) have an answer for allZeros that doesn't force us to keep it around forever. As long as we build the standard library in Swift 3.2 mode, the compiler's current combination of bugs and features allows us to prevent users from actually using it when they build in Swift 4 mode.
|
@swift-ci Please test |
|
@swift-ci Please test source compatibility |
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.
This is not ready for merge yet because, at the very least, we don't (yet) have an answer for
allZerosthat doesn't force us to keep it around forever. As long as we build the standard library in Swift 3.2 mode, the compiler's current combination of bugs and features allows us to prevent users from actually using it when they build in Swift 4 mode.Related radar: rdar://problem/31725206