[swift-evolution] [swift-evolution-announce] [Review] SE-0067: Enhanced Floating Point Protocols

Stephen Canon scanon at apple.com
Fri Apr 22 11:23:33 CDT 2016

> On Apr 22, 2016, at 12:21 PM, Xiaodi Wu <xiaodi.wu at gmail.com> wrote:
> To expand, the hypothetical use case I'm trying to leave open is this:
> suppose I want to implement a Float1024 type with 79 exponent bits and
> 944 fraction bits. Could I conform it to BinaryFloatingPoint? As
> currently proposed, no. What would make it possible would be
> `exponent` of type Self, pushing down RawSignificand to
> BinaryFloatingPoint, and using that associated type for both
> `exponentBitPattern` and `significandBitPattern` (perhaps renaming it
> RawBitPattern).

Right, but why is this any different from a hypothetical FloatingPoint type with 79 exponent bits and 48 significand bits?  If we’re going to be completely general, we should do the completely general thing, not a halfway measure that makes other details more complicated.

– Steve
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160422/228c47af/attachment.html>

More information about the swift-evolution mailing list