0xFF000000_0000000000000 should error with value out of range; instead treated as 0

[timotheecour]

0xFF000000_0000000000000 should error with value out of range; instead treated as 0

Example

block:
  echo 0xFF000000_0000000
  echo 0xFF000000_00000000
  echo 0xFF000000_000000000
  echo 0xFF000000_0000000000
  echo 0xFF000000_00000000000
  echo 0xFF000000_000000000000
  echo 0xFF000000_0000000000000

Current Output

1148417904979476480
-72057594037927936
-1152921504606846976
0
0
0
0

Expected Output

echo 0xFF000000_0000000000

this should give error: value out of range

Additional Information

found that while working on #14522
177c7f9 1.3.5

the fact that 0xFF000000_0000000 is treated as signed instead of unsigned is a separate issue, to be discussed sepately

[alaviss]

the fact that 0xFF000000_0000000 is treated as signed instead of unsigned is a separate issue, to be discussed sepately

IIRC there were proposals to make this uint but was met with enough resistance that it didn't take off.

Maybe now we should re-propose this as an RFC?

[timotheecour]

IIRC there were proposals

do you have a link?
current behavior causes absurdities such as #14522

[alaviss]

I can't find it, though @Araq has said on record many times that hex as int is intentional, so maybe he can expand on the topic.

[Araq]

0xFF000000_00000000.uint64 should be 0xFF000000_00000000'u64. Hex numbers should have suffixes anyway that's why I rejected the proposal.

[ringabout]

Duplicate of #4350