> On Apr 22, 2016, at 12:21 PM, Xiaodi Wu <[email protected]> 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
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
