3 ms·
> uint_32 strikes again! It isn't a uint32, it is an int32. Using strings avoids one problem but introduce a bunch of others (e.g. a string is harder to verif
by Someone1234 12y ago
> uint_32 strikes again!
It isn't a uint32, it is an int32.
Using strings avoids one problem but introduce a bunch of others (e.g. a string is harder to verify, therefore less secure, and therefore needs to be handled with the kiddie gloves). Checking that every character is between 0-9 and dropping all other characters is easy, cheap, and effective. Then just check it is between uint64.Min and uint64.Max, and you're done.
uint32 gives them twice as much capacity (which isn't enough at this stage), they'll likely want to go with a uint64.