File: protocol-conformance-in-extension.swift

package info (click to toggle)
swiftlang 6.1.3-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 2,791,532 kB
  • sloc: cpp: 9,901,743; ansic: 2,201,431; asm: 1,091,827; python: 308,252; objc: 82,166; f90: 80,126; lisp: 38,358; pascal: 25,559; sh: 20,429; ml: 5,058; perl: 4,745; makefile: 4,484; awk: 3,535; javascript: 3,018; xml: 918; fortran: 664; cs: 573; ruby: 396
file content (19 lines) | stat: -rw-r--r-- 864 bytes parent folder | download | duplicates (2) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
 
// RUN: %empty-directory(%t)
// RUN: %target-swift-frontend -enable-objc-interop -emit-module -o %t/a~partial.swiftmodule -I %S/Inputs/custom-modules -module-name TEST -primary-file %s
// RUN: %target-swift-frontend -enable-objc-interop -emit-module -o %t/test.swiftmodule -I %S/Inputs/custom-modules -module-name TEST %t/a~partial.swiftmodule

import TestProtocols

// The protocol in the extension has to refine something that the base class
// conforms to to trigger the error in rdar://problem/32346184.
protocol SomeSwiftProto: Equatable {}
extension ProtocolTestingBase: Equatable {
  public static func ==(left: ProtocolTestingBase, right: ProtocolTestingBase) -> Bool {
    return left === right
  }
}

// The extension going through the typealias also makes a difference.
typealias SpecialObject = SubProtoImpl
extension SpecialObject: SomeSwiftProto {
}