[perl #131256] Re: Configure failure of Rakudo Star Release 2017.04 on ARM

2017-05-05 Thread via RT
# New Ticket Created by Steve Mynott # Please include the string: [perl #131256] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=131256 > With 2017.04 Rakudo Star you need to pass '--no-telemeh' to MoarVM Configure.pl. You the

[perl #131118] [RFC][@LARRY] Implement a way to propagate exceptions in Junctions

2017-05-05 Thread Zoffix Znet via RT
On Fri, 07 Apr 2017 10:08:54 -0700, comdog wrote: > Consider this junction which you probably shouldn't make but you know > will happen in the hands of users: > > any( 5, 'flarg' ) == 5 > > Despite having an element that satisfies the condition, it blows up > because one of them doesn't: > >

[perl #131118] [RFC][@LARRY] Implement a way to propagate exceptions in Junctions

2017-05-05 Thread Zoffix Znet via RT
On Fri, 07 Apr 2017 10:08:54 -0700, comdog wrote: > Consider this junction which you probably shouldn't make but you know > will happen in the hands of users: > > any( 5, 'flarg' ) == 5 > > Despite having an element that satisfies the condition, it blows up > because one of them doesn't: > >

[perl #131261] [@LARRY] phasers/loop controls in routines that accept Callables

2017-05-05 Thread via RT
# New Ticket Created by Zoffix Znet # Please include the string: [perl #131261] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=131261 > I came across an interesting doc Issue[^1] showcasing `next` working inside the Callable

[perl #128201] [BUG] [WEIRD] `.gist` hangs indefinitely on a lazy array passed to a slurpy paramater

2017-05-05 Thread Zoffix Znet via RT
On Fri, 20 May 2016 15:32:02 -0700, sml...@gmail.com wrote: > The .gist call in the following code hangs indefinitely: > > my @a = 1..Inf; foo @a; sub foo(*@_) { say @_.gist }; > > It shouldn't hang, because checking the argument for laziness returns > True, and indexing it does not hang either

[perl #128201] [BUG] [WEIRD] `.gist` hangs indefinitely on a lazy array passed to a slurpy paramater

2017-05-05 Thread Zoffix Znet via RT
On Fri, 20 May 2016 15:32:02 -0700, sml...@gmail.com wrote: > The .gist call in the following code hangs indefinitely: > > my @a = 1..Inf; foo @a; sub foo(*@_) { say @_.gist }; > > It shouldn't hang, because checking the argument for laziness returns > True, and indexing it does not hang either

[perl #131255] [STAR] Configure failure of Rakudo Star Release 2017.04 on ARM

2017-05-05 Thread Zoffix Znet via RT
On Fri, 05 May 2017 02:47:02 -0700, c...@zoffix.com wrote: > On Thu, 04 May 2017 07:41:10 -0700, 1parr...@gmail.com wrote: > > Unfortunately, install processes is broken on ARM (R Pi). The > > configure process has a compile failure. I've attached the output to > > STDERR. > > > > The offending cod

[perl #131255] [STAR] Configure failure of Rakudo Star Release 2017.04 on ARM

2017-05-05 Thread Zoffix Znet via RT
On Fri, 05 May 2017 02:47:02 -0700, c...@zoffix.com wrote: > On Thu, 04 May 2017 07:41:10 -0700, 1parr...@gmail.com wrote: > > Unfortunately, install processes is broken on ARM (R Pi). The > > configure process has a compile failure. I've attached the output to > > STDERR. > > > > The offending cod

[perl #131255] Configure failure of Rakudo Star Release 2017.04 on ARM

2017-05-05 Thread Zoffix Znet via RT
On Thu, 04 May 2017 07:41:10 -0700, 1parr...@gmail.com wrote: > Unfortunately, install processes is broken on ARM (R Pi). The > configure process has a compile failure. I've attached the output to > STDERR. > > The offending code appears to be identical to the 2012.01 version, > which worked. Did

[perl #131255] Configure failure of Rakudo Star Release 2017.04 on ARM

2017-05-05 Thread Zoffix Znet via RT
On Thu, 04 May 2017 07:41:10 -0700, 1parr...@gmail.com wrote: > Unfortunately, install processes is broken on ARM (R Pi). The > configure process has a compile failure. I've attached the output to > STDERR. > > The offending code appears to be identical to the 2012.01 version, > which worked. Did