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
Just to be clear the problem is that casting a NSNumber to Float fails if it can't be cleanly represented in Swift 4.1 but it did not fail in Swift 4.0.
This issue is a duplicate of SR-5179 except that my bug is 4.1 rather than Swift 3.2. It seems like this change was made in Swift 3.2 then reverted later, but this regression has been reintroduced in Swift 4.1
Additional Detail from JIRA
md5: 6665dbaa4e4dc4c365a6afae0801a0f0
Issue Description:
This seems to be the same issue as described here, SR-5179. I also reported a different issue that has the same cause SR-7576
Casting an NSNumber to Float seems to use
The text was updated successfully, but these errors were encountered: