[perl #131492] Camelia produces different error message from commandline

2017-06-02 Thread via RT
# New Ticket Created by Benjamin Goldberg # Please include the string: [perl #131492] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=131492 > On #perl6 IRC, I typed this: m: my \foo = Callable but role :: { }; <+camelia> rak

[perl #131491] Using infix: to set default sometimes ends up as Seq in `where` clause

2017-06-02 Thread via RT
# New Ticket Created by Zoffix Znet # Please include the string: [perl #131491] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=131491 > The issue I encountered is a case where when I assign a default created using infix: op,

[perl #131490] Crash in Junction:D.BUILDALL `This type (Scalar) does not support elems`

2017-06-02 Thread via RT
# New Ticket Created by Zoffix Znet # Please include the string: [perl #131490] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=131490 > While chasing some other bugs, came across this one: m: Junction.new.BUILDALL: {}

[perl #131488] [BUG] .map as return value of sunk Promise doesn't get sunk

2017-06-02 Thread via RT
# New Ticket Created by Zoffix Znet # Please include the string: [perl #131488] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=131488 > Normally, if you sink a .map, it gets eagerly evaluated: m: .map: &say rakudo-m

[perl #123572] [BUG] :256[list of numbers] wrongly allows the numbers to exceed 255 in Rakudo

2017-06-02 Thread Larry Wall via RT
On Fri, 09 Jan 2015 10:59:08 -0800, masak wrote: > m: say :256["☺".ords] > rakudo-moar c5dcdf: OUTPUT«9786␤» > m: say :256[0x263a] > rakudo-moar c5dcdf: OUTPUT«9786␤» > seems we could use a check there... > m: say :256[256,256] > rakudo-moar c5dcdf: OUTPUT«65792␤» > * masak submits rakudobug

[perl #131479] [ASYNC] Proc::Async.kill doesn't seem to work when more than 1 proc is involved

2017-06-02 Thread Zoffix Znet via RT
On Thu, 01 Jun 2017 18:42:03 -0700, c...@zoffix.com wrote: > This appears to hang more often than not, despite printing "Killing" > messages. > > perl6 -e 'await ^2 .map: {start { with Proc::Async.new: $*EXECUTABLE, > "-e", "sleep" -> $p { Promise.in(2).then: {say "Killing"; $p.kill: > SIGTERM}; a

[perl #131479] [ASYNC] Proc::Async.kill doesn't seem to work when more than 1 proc is involved

2017-06-02 Thread Zoffix Znet via RT
On Thu, 01 Jun 2017 18:42:03 -0700, c...@zoffix.com wrote: > This appears to hang more often than not, despite printing "Killing" > messages. > > perl6 -e 'await ^2 .map: {start { with Proc::Async.new: $*EXECUTABLE, > "-e", "sleep" -> $p { Promise.in(2).then: {say "Killing"; $p.kill: > SIGTERM}; a

[perl #131483] [LTA] Inconsistent resultant type of `+@` slurpy when given a Seq

2017-06-02 Thread via RT
# New Ticket Created by Zoffix Znet # Please include the string: [perl #131483] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=131483 > Some discussion: https://irclog.perlgeek.de/perl6-dev/2017-06-02#i_14675550 The crux of i