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
[GSB] Put conformance requirements on the proper potential archetype.
We were putting conformance requirements on the representative of the
equivalence class, rather than directly on the potential archetype on
which the conformance requirement was specified. This violates the
invariant used when forming protocol-requirement sources that we never
reseat a requirement onto the representative (which would
have become a problem when implementing recursive protocol
constreaints) as well as masking a GSB idempotency issue that comes
from same-type requirements where the right-hand side was not
guaranteed to refer to the archetype anchor *within* that subcomponent.
Copy file name to clipboardExpand all lines: validation-test/compiler_crashers_fixed/28730-unreachable-executed-at-swift-lib-ast-astcontext-cpp-1229.swift
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -5,5 +5,5 @@
5
5
// See https://swift.org/LICENSE.txt for license information
6
6
// See https://swift.org/CONTRIBUTORS.txt for the list of Swift project authors
7
7
8
-
// RUN: not --crash %target-swift-frontend %s -emit-ir
8
+
// RUN: not %target-swift-frontend %s -emit-ir
9
9
class a=protocolP{{}typealias e:P}}extensionP{func a{}typealias e:a
0 commit comments