-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
feat(math): Upstream GDA based decimal type - marshal/unmarshal #21016
Conversation
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. 🗂️ Base branches to auto review (1)
Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What are the rules for when e
notation is or isn't used in marshaling? We should be explicit about that... at the risk of writing custom string formatting logic on top of apd
@aaronc ive added in a couple of more tests, let me know if this is suffice. Ive also added in more godocs around restraints and strange behaviour. This less effects unmarshaling |
math/dec.go
Outdated
func (d Dec) Marshal() ([]byte, error) { | ||
return d.dec.MarshalText() | ||
// The output may be in scientific notation if the number's magnitude is very large or very small. | ||
// Specifically, scientific notation is used for numbers with an absolute value >= 1e6 or < 1e-5. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this is used for token values it might be somewhat non-intuitive as these often at least 6 or 9 digits. What are we optimizing for here? Storage space or human readability?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm yes good point. Client libraries would have to handle this notation, too when submitted as json. What do you suggest here re format?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good tests!
I am not sure when it is decimal or scientific notation.
}, | ||
"1e100000": { | ||
x: NewDecWithPrec(1, 100_000), | ||
exp: "1E+100000", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
here and others: I was expecting `"100000000000..." not the scientific notation.
math/dec_test.go
Outdated
exp: "123456", | ||
}, | ||
"Trailing zeros": { | ||
x: "1.23456E+8", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there are no trailing 0 in this example. Something like this 1.00000
or 1.10000
would work
x: "1.23456e+8", | ||
exp: "123456000", | ||
}, | ||
"Zero value": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be good to include -0
as an edge case in the test spec
math/dec_test.go
Outdated
exp string | ||
expErr error | ||
}{ | ||
"No trailing zeros": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about testing leading zeros instead? for example 0123
math/dec.go
Outdated
func (d *Dec) Unmarshal(data []byte) error { | ||
return d.dec.UnmarshalText(data) | ||
func (x *Dec) Unmarshal(data []byte) error { | ||
var d apd.Decimal |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would it make sense to use our string constructor instead? We have a lot of checks there already.
math/dec.go
Outdated
return ErrInvalidDec.Wrap("not a number") | ||
case apd.Infinite: | ||
return ErrInvalidDec.Wrap("infinite decimal value not allowed") | ||
default: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The success case should probably be apd.Finite
, with default:
actually being an error for unknown form
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Description
Closes: #XXXX
Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
!
in the type prefix if API or client breaking changeCHANGELOG.md
Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
Please see Pull Request Reviewer section in the contributing guide for more information on how to review a pull request.
I have...