Hello Chris, When dealing with floating point values, wouldn't it be in our best interest to always be very specific about the accuracy of the floating point type variables we use regardless of the device it runs on? This is the biggest problem I had with CGFloat: while it is nice at first to have a type that adapts to the device word size it runs on, I prefer to always have an explicit accuracy guarantee than worrying about my CGFloat code changing in behaviour when it runs on a 32 bit device rather than a 64 bit one.
Sent from my iPhone > On 6 Jan 2016, at 02:08, Chris Lattner via swift-evolution > <[email protected]> wrote: > > >> On Jan 5, 2016, at 4:41 PM, Janosch Hildebrand via swift-evolution >> <[email protected]> wrote: >> >> I also think that Float and Double are not ideal type names but I also agree >> with many of the concerns that have been raised. >> >> >> Why not simply use (the existing) Float32 and Float64 while keeping >> everything else equal? > > What perceived problem are you solving? > > -Chris > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
