I found a bug in my code that is caused by NSDecimalNumber.notANumber.intValue
returning 9, while I would expect NaN
(as floatValue
or doubleValue
return). Does anybody know why?
Like mentioned by Joakim Danielson and noted in the Apple Developer Documentation
... Because numeric types have different storage capabilities, attempting to initialize with a value of one type and access the value of another type may produce an erroneous result ...
And since Swift's Int
struct cannot represent NaN values, you get this erroneous result.
Instead you could use Int
's Failable Initialiser init(exactly:)
that converts your NSDecimalNumber to an Int?
that will either contain it's value or be nil
if it is not representable by an Int
.
let strangeNumber = NSDecimalNumber.notANumber // nan
let integerRepresentation = Int(exactly: strangeNumber) // nil
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With