> On Jan 6, 2016, at 12:01 AM, Goffredo Marocchi via swift-evolution > <[email protected]> wrote: > 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.
Well, CGFloat has a specific purpose, which is for calculations having to do with things that are drawn on a display. If you need guaranteed precision in your model layer, you should be using Double and convert as needed. -jcr _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
