Skip to content
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

[FEATURE] improving documentation for Int and UInt #55

Open
rrrkren opened this issue Feb 29, 2024 · 0 comments
Open

[FEATURE] improving documentation for Int and UInt #55

rrrkren opened this issue Feb 29, 2024 · 0 comments

Comments

@rrrkren
Copy link
Contributor

rrrkren commented Feb 29, 2024

Issue to be solved

it's not exactly clear according to the documentation what UInt and Int's precisions are.The current doc only mentions that it's an arbitrary size. Doing some digging it seems like the underlying implementation is a big.Int in Go with an initializer that bounds it to int64. This is particularly troublesome when someone needs to sync a piece of on-chain struct/event field into their database while not knowing the precision.

Suggest A Solution

improve documentation so that it's clear to developers what the max value of Int/UInt is. I understand the "arbitrary" argument in the context of Go, but can't wrap my head around this idea in a blockchain where everything is highly deterministic.

What are you currently working on that this is blocking?

No response

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

No branches or pull requests

1 participant