Re: [perl #129862] [BUG][POD] Pod::To::Text failing on uneven row lengths

2016-10-12 Thread Tom Browder
On Wed, Oct 12, 2016 at 3:22 PM, David Warring wrote: > # New Ticket Created by David Warring > # Please include the string: [perl #129862] > # in the subject line of all future correspondence about this issue. > # https://rt.perl.org/Ticket/Display.html?id=129862

[perl #129862] [BUG][POD] Pod::To::Text failing on uneven row lengths

2016-10-12 Thread via RT
# New Ticket Created by David Warring # Please include the string: [perl #129862] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=129862 > Consider pod.pl: =begin pod =begin table a | b | c l | m | n x | y =end table =end

[perl #129772] [LTA] error message when using int parameters as subs

2016-10-12 Thread jn...@jnthn.net via RT
On Fri Sep 30 21:17:55 2016, c...@zoffix.com wrote: > > If you accidentally use an `int` variable as a Callable, you get a > helpful error: > > m: my int $i; $i() > rakudo-moar 1f29cb: OUTPUT«No such method 'CALL-ME' for > invocant of type 'Int'␤ in block at line 1␤␤» > >

[perl #128694] [CONC] Supply.zip-latest locks up two Supply.interval supplies

2016-10-12 Thread jn...@jnthn.net via RT
On Thu Jul 21 14:42:42 2016, moritz wrote: > Consider this code: > > #!/usr/bin/env perl6 > > my $source = Supply.interval(1); > $source.tap({ say 'DEBUG: source'}); > my $heartbeat = Supply.interval(0.7); > $heartbeat.tap({ say 'DEBUG: heartbeat'}); > react { > whenever

[perl #129827] [BUG] method form of `return` errors out instead of returning

2016-10-12 Thread jn...@jnthn.net via RT
On Fri Oct 07 09:39:14 2016, c...@zoffix.com wrote: > > m: sub { 42.return }() > rakudo-moar 605f27: OUTPUT«Attempt to return outside of any > Routine␤ in sub at line 1␤ in block at line 1␤␤» > It was an over-eager return-handler optimization. Fixed, and test added in

[perl #129856] namespace clashes

2016-10-12 Thread Zoffix Znet via RT
I've narrowed down the issue to this condition: if the package's name is part something that we already have in core, then this bug (is it a bug?) appears: No names to clash with core types; everything works: $ cat Foo.pm6 unit package Bar; class Ber {} $ perl6 -I. -MFoo -e 'say

[perl #128863] [CONC] [RFC] [UNI] IO::Socket::Async should support more encodings than UTF-8

2016-10-12 Thread jn...@jnthn.net via RT
On Sat Aug 06 11:59:50 2016, sml...@gmail.com wrote: > To subscribe to incoming data of a connected IO::Socket::Async, the > choices currently are: > > .Supply() -- get UTF-8 decoded data as Str > .Supply(:bin) -- get raw data as Buf > > In analogy to the open() function that takes both :bin and

[perl #129856] namespace clashes

2016-10-12 Thread via RT
# New Ticket Created by mt1957 # Please include the string: [perl #129856] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=129856 > Hi, I wanted to define a class in the 'Pod' package like so (in file lib/Pod/Render.pm6)

Re: [perl #127033] [CONC] threads, dynamic variables lost sometimes

2016-10-12 Thread Lloyd Fournier
Tests: https://github.com/perl6/roast/commit/0705a6ea62a6f1cdaeb6cd46f3130d3728c4ce1b On Tue, Oct 11, 2016 at 9:26 PM Lloyd Fournier wrote: > looks like it's been fixed! \o/ > > I will put writing test for this on my TODO. > > > On Tue, Oct 11, 2016 at 5:00 AM Sam S. via