Skip to content

NSDecimalValue: Dont use .doubleValue for integer properties. #1821

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 14, 2019

Conversation

spevans
Copy link
Contributor

@spevans spevans commented Jan 15, 2019

  • Decimal: Add an internal .int64Value and .uint64Value.

  • NSDecimalValue: For the .intValue and .uintValue properties
    use a truncated value from .int64Value and .uint64Value.

  • Using .doubleValue lost information when returning large numbers

    2e53 due to Double to Int conversion.

  • The returned values mostly match Darwin, moreso than just returning 0
    when an exact conversion cannot be made.

- Decimal: Add an internal .int64Value and .uint64Value.

- NSDecimalValue: For the .int*Value and .uint*Value properties
  use a truncated value from .int64Value and .uint64Value.

- Using .doubleValue lost information when returning large numbers
  > 2e53 due to Double to Int conversion.

- The returned values mostly match Darwin, moreso than just returning 0
  when an exact conversion cannot be made.
@spevans
Copy link
Contributor Author

spevans commented Jan 15, 2019

@swift-ci test

@spevans spevans requested a review from millenomi January 23, 2019 12:54
@millenomi millenomi merged commit 988e631 into swiftlang:master Feb 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants