You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm afraid we're going to use boxing here, like Google did, since you cannot do better.
However, since JavaScript can't send 'long long' values and that you cannot return 'long long' values to JavaScript (you'll be restricted by what a Number can hold), this does not really matter: the LongLong type can only be used inside an API.
We can include support for long long as something optional that uses boxing and rely on Google's implementation (ie: if you want to make a polyfill using long long, then you need to include the Google API for it to work, or you accept to loose precision during the calculations).
I think that that is fine. Like you said, there is no use case for long long in JS itself - only for something that would be running boxed (or in C++).
So we should just de-prioritize supporting this altogether for now and maybe just throw an NotSupportedError.
http://www.w3.org/TR/WebIDL/#idl-long-long
The text was updated successfully, but these errors were encountered: