-
Notifications
You must be signed in to change notification settings - Fork 346
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
Decimal256 #1067
Decimal256 #1067
Conversation
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.
Nice stuff. I'm not so sure about the change from 18 decimal places to 36. Let's see what community says.
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.
lgtm.
Alright, the two open changes:
Then 🚀 |
Rebased. |
CHANGELOG.md
Outdated
@@ -21,6 +21,7 @@ and this project adheres to | |||
`Into<Uint128>` rather than `Into<u128>`. | |||
- cosmwasm-crypto: Update dependency `k256` to ^0.9.6. | |||
- cosmwasm-std: Add enum cases `Shl` to `OverflowOperation` (breaking; [#1071]). | |||
- cosmwasm-std: `Decimal256` now has 18 decimal places. |
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.
I think we can drop this as Decimal256
is newly created in this PR
Co-authored-by: Simon Warta <[email protected]>
CHANGELOG.md
Outdated
@@ -40,6 +41,7 @@ and this project adheres to | |||
`Uint64`, `Uint128`, `Uint256`, and `Uint512`. | |||
- cosmwasm-std: Exposed `Uint{64, 128, 256}::full_mul` for full multiplication | |||
that cannot overflow. | |||
- cosmwasm-std: Added the `Decimal256` type with 18 decimal places. |
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.
Ah, I guess this ended up in the wrong section after the rebase and got me confused. Let's fix this...
Whew. We've got our own
Decimal256
.Addresses #1052. I'm not sure if there's any more work there except for getting this PR in. I'll review tomorrow.Closes #1052