You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that the diagnostics are automatically errors in Swift 6, we don't need an
`-enable-conformance-availability-errors` flag to control whether unavailable
conformances are diagnosed as errors. Nobody was using the flag so it should be
safe to remove.
Part of rdar://88210812
Copy file name to clipboardexpand all lines: test/Sema/conformance_availability_warn.swift
+7-7
Original file line number
Diff line number
Diff line change
@@ -19,10 +19,10 @@ public struct HasAvailableConformance1 {}
19
19
@available(macOS 100,*)
20
20
extensionHasAvailableConformance1:Horse{}
21
21
22
-
// These availability violations are warnings because this test does not
23
-
// pass the -enable-conformance-availability-errors flag. See the other
24
-
// test case in test/Sema/conformance_availability.swift for the same
25
-
// example but with this flag.
22
+
// These availability violations are warnings because this test does not pass
23
+
// -swift-version 6.
24
+
// See the other test case in test/Sema/conformance_availability.swift for the
25
+
// same example but with -swift-version 6.
26
26
27
27
func passAvailableConformance1(x:HasAvailableConformance1){ // expected-note 6{{add @available attribute to enclosing global function}}
28
28
takesHorse(x) // expected-warning {{conformance of 'HasAvailableConformance1' to 'Horse' is only available in macOS 100 or newer; this is an error in Swift 6}}
@@ -60,9 +60,9 @@ public struct HasAvailableConformance2 {}
60
60
extensionHasAvailableConformance2:Horse{} // expected-note 6 {{conformance of 'HasAvailableConformance2' to 'Horse' has been explicitly marked unavailable here}}
61
61
62
62
// Some availability diagnostics become warnings in Swift 5 mode without
63
-
// -enable-conformance-availability-errors because they were incorrectly
64
-
// accepted before and rejecting them would break source compatibility. Others
65
-
// are unaffected because they have always been rejected.
63
+
// because they were incorrectly accepted before and rejecting them would break
64
+
// source compatibility. Others are unaffected because they have always been
0 commit comments