Remove classic whole-project compiler invocations. #9332
Merged
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
This feature was off-by default in Swift 6.0 This patch completes the transition to precise compiler invocations by removing the backwards-compatibility. The many test updates are for tests that were checking for the old behavior (which was still present in the tests due to the typeref-typesystem validation creating an classic-mode scratch context).
adrian-prantl
requested review from
kastiglione,
augusto2112 and
felipepiovezan
|
test with swiftlang/swift#76703 |
adrian-prantl
merged commit 1b3ed00
into
swiftlang:stable/20240723
1 of 3 checks passed
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 feature was off-by default in Swift 6.0
This patch completes the transition to precise compiler invocations by removing the backwards-compatibility.
The many test updates are for tests that were checking for the old behavior (which was still present in the tests due to the typeref-typesystem validation creating an classic-mode scratch context).