-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
BigInt Support #29
Comments
js-api spec says BigInt is coerced to wasm types (i32, i64, f32, f64). So we don't need to care over 64bits case. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As part of #26, I created an API that uses BigInt values in some cases. They are not currently implemented, however. An important design question is whether bey should be represented as Int64/UInt64 — sacrificing precision for code size and ease of use — or whether some sort of BigInt library should be made a dependency so we can guarantee precision at the cost of code size and performance.
The text was updated successfully, but these errors were encountered: