Closed japanoise closed 5 years ago
I'd also like to have some way of coercing values to uint64 without just relying on overflows.
I agree. I don't like the range overflow for creation. How about the old C++ designation with a ULL
suffix to designate uint64:
(def a 0ULL) // 0 in an uint64
and a coercion function
(asUint64 x)
integrated into releases v5.0.9 and v5.1.0.
Addresses my own feature request, #39
The tests could probably do with some work and it definitely needs a once-over from the maintainer, though. I'd also like to have some way of coercing values to uint64 without just relying on overflows.