am looking at it
> On 19 Mar 2017, at 22:03, Aleks-Daniel Jakimenko-Aleksejev (via RT)
> wrote:
>
> # New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
> # Please include the string: [perl #131018]
> # in the subject line of all future correspondence about this issue.
> # https://rt.pe
This issue was about a failing test for too large unicode code points.
#?rakudo.moar todo 'chr max RT #124837'
dies-ok {chr(0x10+1)}, "chr out of range (max)";
Ticket https://rt.perl.org/Ticket/Display.html?id=130914 has more informations,
so I'm closing this one as a duplicate.
I started to add a test or two for this issue, but then I found the following
test in S29-conversions/ord_and_chr.t:
#?rakudo.moar todo 'chr max RT #124837'
dies-ok {chr(0x10+1)}, "chr out of range (max)";
Looking at https://en.wikipedia.org/wiki/Code_point and
http://www.unicode.org/gl
# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
# Please include the string: [perl #131018]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131018 >
Code:
.say for .rotor(2 => -2, 1)
Result (2015.12..2016.12):
(a b)
On Wed, 15 Mar 2017 20:30:28 -0700, alex.jakime...@gmail.com wrote:
> Maybe this can help:
>
> ==8544==
> ==8544== Invalid read of size 8
> ==8544== at 0x4FD4B87: MVM_nativecall_refresh (nativecall.c:753)
> ==8544== by 0x4FD6BCD: MVM_nativecall_invoke (nativecall_dyncall.c:780)
> ==8544== by 0x4FA