[swift-evolution] undefined

Haravikk swift-evolution at haravikk.me
Thu Jan 28 05:24:59 CST 2016

I agree, I think this would require all integer types to have mandatory init(_:IntMax), init(_:UIntMax), init(truncatingBitPattern:IntMax) and init(truncatingBitPattern:UIntMax) constructors? Would make working with arbitrary sized integers in a generic way a lot easier.

> On 28 Jan 2016, at 04:02, Patrick Pijnappel via swift-evolution <swift-evolution at swift.org> wrote:
> It seems IntegerArithmeticType should have a conversion from IntMax, in analogy with Signed/UnsignedIntegerType. It already has toIntMax(), but not the reverse conversion. This is important to be able to write generic algorithms on IntegerArithmeticType. Are there any reasons it shouldn't?
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160128/26e520a2/attachment.html>

More information about the swift-evolution mailing list