You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From my point of view, it's really annoying that all values are encoded and decoded as double, in some cases this behaviour might be even buggy.
I propose to let caller side decide how to unwrap returned Number - as Double, Int, whatever
The text was updated successfully, but these errors were encountered:
Nice idea.
It did bothered me, too.
In one of the first commits it was a NSNumber, But, I Changed that later.
Because I don't want any NSThings come out from the value ------ The Cocoa things always comes with implicitly-unwrapped-optionals. Which I think , is not following the fundamental ideas of Swift language.
If there has a way simple and explicit as basic types yet functional as NSNumber, I'd be very happy to use that.
I need a few time to think about it.
From my point of view, it's really annoying that all values are encoded and decoded as
double
, in some cases this behaviour might be even buggy.I propose to let caller side decide how to
unwrap
returned Number - as Double, Int, whateverThe text was updated successfully, but these errors were encountered: