From @masak

<diakopter> masak​: here's a fun one​:
<diakopter> r​: $1111111111111111111
<p6eval> rakudo 1c9939​: OUTPUT«Cannot use negative index -2147483648
on Any [...]
<jnthn> I see these are submissions to be tagged [WEIRD] :P
<diakopter> r​: $2147483647
<p6eval> rakudo 1c9939​: ( no output )
<diakopter> r​: $2147483648
<p6eval> rakudo 1c9939​: OUTPUT«Cannot use negative index -2147483648 [...]
* masak submits rakudobug

From @usev6

For Moar the limit now seems to be at 2**63 - 2**9 (on a 64-bit system)​:

$ perl6-m -e '$9223372036854775295'
$ perl6-m -e '$9223372036854775296'
Unhandled exception​: Calculated index (-9223372036854775808) is negative, but Any allows only 0-based indexing
[...]

For Parrot the limit seems to be 2**63 - 2**10 + 2**7 - 2**4 + 2**2 (don't ask)​:

$ perl6-p -e '$9223372036854774899'
$ perl6-p -e '$9223372036854774900'
Calculated index (-9223372036854775808) is negative, but Any allows only 0-based indexing
[...]

JVM can handle even larger numbers as variable names​:

$ perl6-j -e '$92233720368547752960000'

I guess the error message comes from trying to access the respective element of $/ via a subscript​: When we get an integer overflow we also get said error message since negative subscripts are not allowed.

So, what shall be done about this? I don't think it's worth it to generate a special error message for such large capture variables.

@usev6 - Status changed from 'new' to 'open'

From @diakopter

14​:14 <diakopter> m​: $9223372036854775296
14​:14 <camelia> rakudo-moar 61d231​: ( no output )
14​:15 <diakopter> m​: $922337203685477529623423423423423423234234234234234
14​:15 <camelia> rakudo-moar 61d231​: ( no output )

@diakopter - Status changed from 'open' to 'resolved'