Inconsistent error for chr with large codepoints

[zoffixznet]

The first error says stuff's out of bounds and states what the maximum is. The other just says the number's too large.

<Zoffix_> m: dd chr 2**30
<camelia> rakudo-moar ca5825b4f: OUTPUT: «Error encoding UTF-8 string: could not encode codepoint 1073741824 (0x40000000), codepoint out of bounds. Cannot encode higher than 1114111 (0x10FFFF)␤  in block <unit> at <tmp> line 1␤␤»

<Zoffix_> m: dd chr 2**32
<camelia> rakudo-moar ca5825b4f: OUTPUT: «chr codepoint 4294967296 (0x100000000) is too large␤  in block <unit> at <tmp> line 1␤␤»

Also, both throw X::AdHoc; if there's a way to throw something typed instead that'd be even better. (spotted during 6.d review of Raku/roast@fbdb81807 so if we get a typed exception that test can simply be modified)

[lizmat]

Made the error (almost) the same: c8db35e32a .

This should make it easier to test for the error, but making a typed Exception for both cases appears a bit more difficult as it would involve stuff in NQP, probably MoarVM.

So afaiac, we can close this ticket now.

[AlexDaniel]

So-o-o… I'm not sure if this is resolved. I think the idea for the OP was that error messages should be the same? But…

say chr 2**30

Error encoding UTF-8 string: could not encode codepoint 1073741824 (0x40000000), codepoint out of bounds. Cannot encode higher than 1114111 (0x10FFFF)
  in block <unit> at -e line 1

say chr 2**32

Error encoding UTF-8 string: could not encode codepoint 4294967296 (0x100000000), codepoint out of bounds.
  in block <unit> at -e line 1

I mean, if they're different anyway but we say that it's OK, then what was the issue with the original message?