Mirror of forum.nim-lang.org

5385 :: why hexadecimal literals are strictly signed int by default

[2019-10-22T17:22:00+02:00]

mrgaturus (orginal) [2019-10-22T17:22:00+02:00] view original

While creating GL bindings using glad i get some compile errors with two constants of type uint64 that has 0xFFFFFFFFFFFFFFFF, it says type mismatch: got <int literal(-1)> but expected 'uint64, the problem was fixed putting 'u64 at the end but i wonder how this is strictly a signed int, as far i known hexadecimal numbers are mostly used in unsigned scenarios

Araq (orginal) [2019-10-22T17:49:44+02:00] view original

Because the typing rules for literals are independent of the literal representation you use. Back then this seemed to be the most simple, consistent rule. I doubt changing it to uint would help, you're better off with the explicit suffixes anyway.