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
In #41054, we fixed an oversight which caused us to not notice when a user erased a concrete type to an existential using an unavailable conformance. Unfortunately, this is source-breaking and needs to be reduced to a warning in Swift 5 mode unless the user opts in.
Fixes rdar://91940820.
extensionHasAvailableConformance2:Horse{} // expected-note 6 {{conformance of 'HasAvailableConformance2' to 'Horse' has been explicitly marked unavailable here}}
61
+
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.
0 commit comments