Files
swift-mirror/test/Sema/option-set-empty.swift
Robert Widmann 847930bfb7 Don't Force the Interface Type While Checking Sendable
Asking for Sendable conformances on this path is going to lead to
a traversal of the stored properties of the type. If there is an
interface type computation ongoing, as is very likely the case, this
traversal can wind up causing a cycle when it forces the interface type
of a member once again.

Request only the non-structural conformances to break the cycle.

rdar://77189542
2021-04-29 13:11:32 -07:00

33 lines
1.2 KiB
Swift

// RUN: %target-typecheck-verify-swift -verify-ignore-unknown
struct SomeOptions: OptionSet {
var rawValue: Int
static let some = MyOptions(rawValue: 4)
static let empty = SomeOptions(rawValue: 0) // expected-warning {{static property 'empty' produces an empty option set}} expected-note {{use [] to silence this warning}}{{35-48=([])}}
static var otherVal = SomeOptions(rawValue: 0)
let someVal = MyOptions(rawValue: 6)
let option = MyOptions(float: Float.infinity)
let none = SomeOptions(rawValue: 0) // expected-error {{value type 'SomeOptions' cannot have a stored property that recursively contains it}}
}
struct MyOptions: OptionSet {
let rawValue: Int
init(rawValue: Int) {
self.rawValue = rawValue
}
init(float: Float) {
self.rawValue = float.exponent
}
static let none = MyOptions(rawValue: 0) // expected-warning {{static property 'none' produces an empty option set}} expected-note {{use [] to silence this warning}}{{32-45=([])}}
static var nothing = MyOptions(rawValue: 0)
static let nope = MyOptions()
static let other = SomeOptions(rawValue: 8)
static let piVal = MyOptions(float: Float.pi)
static let zero = MyOptions(float: 0.0)
}