-
Notifications
You must be signed in to change notification settings - Fork 165
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
Intent use number / bigint union type #1426
Comments
CC @littledan who added the wording about these union types. |
I'd be curious to hear @littledan's take, but this seems reasonable to me. Thanks for filing! |
Closing this since we have gone ahead with this change now on the wasm side. |
FYI, we ended up reverting this in WebAssembly/memory64#86 because the special conversion rules for a union of numeric type and bigint would, through ToNumeric/ToNumber, force all string and boolean values to be interpreted as Number instead of BigInt. This is a very confusing special case. |
In WebAssembly we are planning on using the union of long long and bigint: WebAssembly/memory64#75
In accordance with the warning in https://webidl.spec.whatwg.org/#idl-union we are opening this issue.
I believe that our use case doesn't run into any issues because we are essentially implementing overloading based on the type of the receiver. The receiver is either a 64-bit memory/table (in which case we expect bitint indexes) or a 32-bit memory/table (in which case we expect number indexes).
The text was updated successfully, but these errors were encountered: