Attachment: Download

Issue Description:

In Swft 5.1, this compiles just fine:

extension ClosedRange {
    /// Return the argument clamped to this range.
    /// Specifically, returns: `max(min(e, self.upperBound), self.lowerBound)`.
    func clamp(_ e: Element) -> Element {
        return Swift.max(Swift.min(e, upperBound), lowerBound)
    }
}

print((0...1).clamp(10) as Double)

But in Swift 5.2, these errors are shown:

closed-range.swift:4:33: error: type 'Bound' does not conform to protocol 'Strideable'
    func clamp(_ e: Element) -> Element {
                                ^
closed-range.swift:4:21: error: type 'Bound' does not conform to protocol 'Strideable'
    func clamp(_ e: Element) -> Element {
                    ^

The errors can be worked around by replacing Element with Bound in the original example. That's odd because Element is a typealias for Bound: https://developer.apple.com/documentation/swift/closedrange/element

That documentation says:
Available when Bound conforms to Strideable and Bound.Stride conforms to SignedInteger.

Not really sure what's going on here. I can understand why the compiler might prefer Bound over Element here (Element is really for the Sequence conformance) and I'm actually happier using Bound here. But I'm not sure why this has changed. I see nothing in the release notes suggesting this change. So I thought I might as well report it.