File: collection-mutablecollection-order-dependency-2.swift

package info (click to toggle)
swiftlang 6.0.3-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 2,519,992 kB
  • sloc: cpp: 9,107,863; ansic: 2,040,022; asm: 1,135,751; python: 296,500; objc: 82,456; f90: 60,502; lisp: 34,951; pascal: 19,946; sh: 18,133; perl: 7,482; ml: 4,937; javascript: 4,117; makefile: 3,840; awk: 3,535; xml: 914; fortran: 619; cs: 573; ruby: 573
file content (22 lines) | stat: -rw-r--r-- 723 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
// RUN: %target-typecheck-verify-swift

// rdar://problem/29954938 -- A bug in associated type inference exposed an
// order dependency where, if a type conformed to Collection in one extension
// then conformed to MutableCollection in a later extension, it would fail
// to type-check. This regression test ensures that a "working" order,
// where MutableCollection comes first, remains working.

struct Butz { }

extension Butz: MutableCollection {
    public var startIndex: Int { return 0 }
    public var endIndex: Int { return 0 }
}

extension Butz: Collection {
    public subscript (_ position: Int) -> Int {
        get { return 0 }
        set {  }
    }
    public func index(after i: Int) -> Int { return 0 }
}