We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
ES2020 adds the BigInt type, which allows for integers outside the ‑253...253 ‑ 1 to be represented in JavaScript code.
BigInt
‑253...253 ‑ 1
This makes it possible to handle the full range of long long and unsigned long long values in JavaScript.
long long
unsigned long long
The text was updated successfully, but these errors were encountered:
Please see #525
Sorry, something went wrong.
And in particular, the decision there was that BigInt will be a separate type not passable to operations taking integers, for consistency with ES.
I assume you meant long long and unsigned long long, by the way, since the full range of long and unsigned long is not a problem in the ES bindings.
long
unsigned long
Yeah, I keep mistakenly thinking of the Java long type, which is an i64, whereas WebIDL uses the C long, which is an i32.
i64
i32
I suggest we rename them to remove this confusion: #843.
Let's dupe this into that PR.
No branches or pull requests
ES2020 adds the
BigInt
type, which allows for integers outside the‑253...253 ‑ 1
to be represented in JavaScript code.This makes it possible to handle the full range of
long long
andunsigned long long
values in JavaScript.The text was updated successfully, but these errors were encountered: