Re: [whatwg/webidl] Intent to use bigint/numeric union (#959)

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 (https://github.com/webmachinelearning/webnn/issues/442)
- clamping a range (https://github.com/webmachinelearning/webnn/issues/442)
- filling in a tensor with sequential values (https://github.com/webmachinelearning/webnn/issues/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](https://github.com/whatwg/webidl/issues/new?title=Intent%20to%20use%20bigint/numeric%20union) before using this feature.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/webidl/issues/959#issuecomment-1949544428
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/webidl/issues/959/1949544428@github.com>