Intent to use bigint/numeric union

[namm356]

No description provided.

[annevk]

Where?

[fdwr]

We have 3 use cases in WebNN where we need to be able to accept full precision from the API and retain it passed all the way down to the bottom, because float64 cannot express the full precision of int64.

• adding padding (Type of some parameters should match the input data type webmachinelearning/webnn#442)
• clamping a range (Type of some parameters should match the input data type webmachinelearning/webnn#442)
• filling in a tensor with sequential values (Constant sequential filling operation needs output shape parameter webmachinelearning/webnn#492)

Since this issue is closed, should I open a new one, per the wording here that @inexorabletash pointed out?

https://webidl.spec.whatwg.org/#limit-bigint-numeric-unions

It would not be appropriate to accept such a union, only to then convert values of the numeric type to a bigint for further processing, as this runs the risk of introducing precision errors. Please file an issue before using this feature.

[inexorabletash]

I expect it was a bot clicking on the link in WebIDL that caused this specific issue to be opened. But for WebNN we've got a real case now! We can either recycle this issue or create a new one, whatever the WebIDL maintainers prefer. Tagging @annevk just in case.

[annevk]

A new issue would be good, thanks!

[fdwr]

A new issue would be good, thanks!

👍 #1388