Is there an effective way to represent a 64-bit Unsigned Integer in Pkl?

[xerotolerance]

Hello Pkl Team,
I am modeling some Kubernetes CRDs for Istio Service Mesh in Pkl as part of a larger project.
I am doing this by hand for now until the k8s.contrib.crd module becomes capable of handling anyOf, oneOf, & the like 😄.

One of the Istio classes I need has a property of type uint64, however the largest int type I see referenced in the Pkl API is int (64-bit signed).

Do you have any recommendations on handling UInt64 at this time?

[HT154]

Because all of Pkl's (U)Int?? types are range-constrained type aliases of Int, they're all stored signed (and 64 bits) under the hood. Supporting UInt64 (or even other larger integers) is definitely a current, known shortcoming of the language and I'd encourage you to file an issue about it!

Similar needs have come up in the past. pkl.experimental.net needs a UInt128 implementation to work with IPv6 addresses and it uses a class composed of 4 UInts to do so: https://github.com/apple/pkl-pantry/blob/main/packages/pkl.experimental.net/u128.pkl

[xerotolerance]

/// Who was it that said we'd never need more than 64 bits??
^ Classic 🤣 .

Thanks @HT154 , pkl.experimental.net/u128.pkl will prove helpful for my use case.
I will file an issue after the workday 💼