Use BigDecimal#precision instead of BigDecimal#precs when available #54
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
v2kovac
reviewed
Mar 13, 2024
| @@ -21,7 +21,7 @@ def to_message(object, field) | |||
| field.subtype.msgclass.new( | |||
| numerator: rational.numerator, | |||
| denominator: rational.denominator, | |||
| precision: object.precs[0], # This is the current precision of the decimal | |||
| precision: object.try(:precision) || object.precs[0], # This is the current precision of the decimal | |||
There was a problem hiding this comment.
this isn't returning the same value for a basic example like
a = BigDecimal("0.123")
a.precision => 3
a.precs[0] => 9
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ruby 3.3.1 moves this method into #precision and #n_significant_digits -
precsgives wildly different results between versions/platforms, this is an important fix IMO.