In UIKit/Cocoa, there's CGFloat that does pretty much what you're asking (and it's pain working with it in Swift, since it's Double on 64-bit computers, while Swift defaults to Float, so you need casting all the time)... And I think the default behavior of Swift should be similar.
I wouldn't change the type names since Double still is "double precision", I'd just prefer changed default behavior... Charlie > On May 24, 2016, at 5:39 AM, David Sweeris via swift-evolution > <[email protected]> wrote: > > >> On May 23, 2016, at 9:55 PM, Xiaodi Wu <[email protected] >> <mailto:[email protected]>> wrote: >> >> On Mon, May 23, 2016 at 9:40 PM, David Sweeris <[email protected] >> <mailto:[email protected]>> wrote: >> >> Have we (meaning the list in general, not you & me in particular) had this >> conversation before? This feels familiar... >> >> It does, doesn't it? I've been reading this list for too long. > I just checked, and we have! In this very thread! I didn’t realize it was > started almost 6 months ago… > > Out of curiosity, are there plans for Swift's IntegerLiteralType & > FloatingPointLiteralType when CPUs eventually support 128-bit ints & floats? > Will they still evaluate to “Int64" and “Double” by default, or will they > become the bigger types? > > - Dave Sweeris > _______________________________________________ > 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
