Right, SE-0067 included that initializer with the caveat that implementation
wouldn't be possible until the integer protocols were revised. As far as I can
see, that makes this a fix that wouldn't need further SE discussion. (The
generic init(exactly:) needs an implementation, too.)
https://github.com/apple/swift-evolution/blob/master/proposals/0067-floating-point-protocols.md
Nate
> On Jan 1, 2018, at 7:01 PM, Xiaodi Wu via swift-evolution
> wrote:
>
> This would be a good addition to the BinaryFloatingPoint protocol. It's not
> difficult to implement; it's not present (afaict) simply because
> BinaryFloatingPoint was designed before BinaryInteger existed.
>
>
>> On Mon, Jan 1, 2018 at 3:58 PM, Kelvin Ma via swift-evolution
>> wrote:
>> title says it all,, this is kind of annoying when writing some generic
>> FloatingPoint code where both the integral and floating parameters are
>> unfixed.
>>
>> ___
>> swift-evolution mailing list
>> swift-evolution@swift.org
>> https://lists.swift.org/mailman/listinfo/swift-evolution
>>
>
> ___
> swift-evolution mailing list
> swift-evolution@swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
___
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution
