[swift-evolution] Is there a need for a Decimal type?
dalebuckley86 at gmail.com
Sat Feb 13 16:46:54 CST 2016
> Cc:swift-evolution at swift.org
> Subject:[swift-evolution] Is there a need for a Decimal type?
> Date:13 February 2016 at 20:45:46 GMT
> Both the NSDecimalNumber class and the NSDecimal struct are already available in Swift. If there were a set of operators and initializers for NSDecimal, would that provide most of what you need? The operators would be simple to implement over the existing functions, I think. Maybe the corelibs people would take those as a patch?
> > On Feb 13, 2016, at 3:51 AM, Dale Buckley via swift-evolution<swift-evolution at swift.org>wrote:
> > We all know the problems with floating point types, they are well documented and well understood by developers everywhere. We know when to use them and (hopefully) when not to use them and if you are working with financial values on a Foundation based platform you know to not use a floating point type and to use NSDecimalNumber instead.
> > My question is this; should there be an equivalent NSDecimalNumber type built into Swift that can be used for precision sensitive decimal values where floating point types can’t be used?
> > Maybe the answer isn’t an ‘equivalent’ as such, it would probably have a modern twist so I can see it looking like something else entirely, but the point still stands.
> > I feel like there is a need for this, it’s not a new problem and has been solved many times over in other languages such as Objective-C (NSDecimalNumber) and Java (BigDecimal) etc. Yet as it stands we seem to be lacking an equivalent solution in Swift. It shouldn’t be left for an external library to solve, it’s one of those things that need to be built into the language.
> > What are peoples thoughts on this?
> > _______________________________________________
> > swift-evolution mailing list
> > swift-evolution at swift.org
> > https://lists.swift.org/mailman/listinfo/swift-evolution
I have been using what Foundation provides up until now. You are indeed correct that add the appropriate operators is a simple task to make it easier to use.
What my original discussion was aimed at was non Foundation based platforms where we don’t have this luxury.
More information about the swift-evolution