mirror of
https://github.com/apple/swift.git
synced 2025-12-14 20:36:38 +01:00
c739ab127c
We have various hacks in the constraint solver to improve the compile-time performance characteristics of operators. Some of those didn't respect availability annotations, causing us to incorrectly choose an unavailable operator when available options exist. Fixes rdar://problem/31592529.
32 lines
822 B
Swift
32 lines
822 B
Swift
// RUN: %target-typecheck-verify-swift -swift-version 4
|
|
|
|
|
|
// rdar://problem/31592529
|
|
infix operator <=< : BitwiseShiftPrecedence
|
|
infix operator >=> : BitwiseShiftPrecedence
|
|
|
|
public protocol P {}
|
|
|
|
extension P {
|
|
public static func <=< <Other : P>(_ x: Self, _ y: Other) { }
|
|
|
|
@available(swift, obsoleted: 4)
|
|
public static func >=> <Other : P>(_ x: Self, _ y: Other) { }
|
|
}
|
|
|
|
extension Int : P {}
|
|
extension Int32 : P {}
|
|
|
|
extension Int32 {
|
|
@available(swift, obsoleted: 4)
|
|
public static func <=< (_ x: Int32, _ y: Int32) {}
|
|
|
|
@available(swift, obsoleted: 4)
|
|
public static func >=> (_ x: Int32, _ y: Int32) {} // expected-note{{'>=>' was obsoleted in Swift 4}}
|
|
}
|
|
|
|
func testAvailability() {
|
|
_ = (1 as Int32) <=< (1 as Int32) // okay
|
|
_ = (1 as Int32) >=> (1 as Int32) // expected-error{{'>=>' is unavailable}}
|
|
}
|