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
The highest u64 value (18446744073709551615) cannot be represented with the current Token::IntegerLiteral(i64).
u64
Token::IntegerLiteral(i64)
One would probably need SignedIntegerLiteral(i64) as well as UnsignedIntegerLiteral(u64). Or you could use on of the 128 bit types.
SignedIntegerLiteral(i64)
UnsignedIntegerLiteral(u64)
The text was updated successfully, but these errors were encountered:
Do you have any preference to the two fixes?
Sorry, something went wrong.
I think the two variant version matches the grammar most closely. It is also extensible, should WebIDL ever allow 128 bit tokens.
af775b1
@jrakow Can you confirm the fix is what you want before I push a new version?
This uses u64 as fallback and all the values in the spec can be represented now. So yeah, looks good to me.
Version 0.7.0 should have the fix. Thanks for the report.
No branches or pull requests
The highest
u64
value (18446744073709551615) cannot be represented with the currentToken::IntegerLiteral(i64)
.One would probably need
SignedIntegerLiteral(i64)
as well asUnsignedIntegerLiteral(u64)
.Or you could use on of the 128 bit types.
The text was updated successfully, but these errors were encountered: