Files
swift-mirror/validation-test/Sema/issue-60958.swift
Erik Eckstein 7cceaff5f3 SIL: don't print operand types in textual SIL
Type annotations for instruction operands are omitted, e.g.

```
  %3 = struct $S(%1, %2)
```

Operand types are redundant anyway and were only used for sanity checking in the SIL parser.

But: operand types _are_ printed if the definition of the operand value was not printed yet.
This happens:

* if the block with the definition appears after the block where the operand's instruction is located

* if a block or instruction is printed in isolation, e.g. in a debugger

The old behavior can be restored with `-Xllvm -sil-print-types`.
This option is added to many existing test files which check for operand types in their check-lines.
2024-11-21 18:49:52 +01:00

37 lines
1.1 KiB
Swift

// RUN: %target-swift-frontend -Xllvm -sil-print-types -emit-silgen %s | %FileCheck %s
// https://github.com/apple/swift/issues/60958
// Make sure that `makeIterator` witness is picked over the non-witness.
struct S: Sequence {
private var _storage: [UInt8] = []
func makeIterator() -> Array<UInt8>.Iterator {
_storage.makeIterator()
}
typealias Element = UInt8
class Iterator: IteratorProtocol {
func next() -> UInt8? { 0 }
typealias Element = UInt8
}
func makeIterator() -> Iterator {
Iterator()
}
}
extension S {
// CHECK: sil hidden [ossa] @$s4main1SV1fyyF
func f() {
for elt in self {
// CHECK: [[ITERATOR_VAR:%.*]] = project_box {{.*}} : ${ var S.Iterator }, 0
// CHECK: [[MAKE_ITERATOR_REF:%.*]] = function_ref @$s4main1SV12makeIteratorAC0C0CyF : $@convention(method) (@guaranteed S) -> @owned S.Iterator
// CHECK-NEXT: [[ITERATOR:%.*]] = apply [[MAKE_ITERATOR_REF]](%0) : $@convention(method) (@guaranteed S) -> @owned S.Iterator
// CHECK-NEXT: store [[ITERATOR]] to [init] [[ITERATOR_VAR]] : $*S.Iterator
print(elt)
}
}
}