[perl #129153] [JVM] Weird spectest failure in S03-metaops/reduce.t (probably wrong multi sub selected)

2016-08-31 Thread via RT
# New Ticket Created by Christian Bartolomaeus # Please include the string: [perl #129153] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=129153 > With rakudo commit b1c444f062 the following test started to fail in S03-metaop

Re: [perl #129131] [RFC] Make .. a numeric operator, please (.say for ‘42’..‘51’)

2016-08-31 Thread Parrot Raiser
The behaviour's hardly "weird"; the loop is operating on the individual digits in a predictable way, $ perl6 -e ".say for '42'..'51';" generates 42 41 52 51 That may be more obvious for slightly different values. $ perl6 -e ".say for '34'..'51';" 34 33 32 31 44 43 42 41 54 53 52 51 That may or m

[perl #118607] [LTA] Suggest multi in "redeclaration of sub foo" error

2016-08-31 Thread Will Coleda via RT
On Tue Aug 30 10:07:57 2016, ddgr...@gmail.com wrote: > On Sun Jun 23 04:26:36 2013, Ayiko wrote: > > use v6; > > sub foo() { say 'hi'; }; > > sub foo($i) { say "hi $i"; }; > > foo(); > > > > Gives as error > > ===SORRY!=== > > Redeclaration of routine foo > > at test2.pl:3 > > --> sub foo($i)

[perl #114388] LTA error when using s[] = "rea"

2016-08-31 Thread Will Coleda via RT
On Fri Apr 17 03:58:32 2015, barto...@gmx.de wrote: > The first evaluation fails again (no method 'subst-mutate' nowadays), > so I'm re-opening this ticket. > > $ perl6 -e 's[ea] = "rea";' > Method 'subst-mutate' not found for invocant of class 'Any' > in block at -e:1 > > We're back to "We co

[perl #129120] [CONC] in await: Cannot invoke this object (REPR: Null; VMNull)

2016-08-31 Thread jn...@jnthn.net via RT
On Wed Aug 31 04:31:25 2016, nicholas wrote: > "my" machine has almost as many cores. I can get it to bomb at times. > (ASAN makes no comment) > Yeah, I'm guessing it's a slightly higher level data race due to mis-code-gen rather than any kind of memory corruption. > > Any chance you could: > >

[perl #129120] [CONC] in await: Cannot invoke this object (REPR: Null; VMNull)

2016-08-31 Thread Zoffix Znet via RT
Attached 'backtrace-original.txt' is the output from the added CATCH and --ll-exception. I was able to golf it down to this: await do for 3¹²³⁴⁵ … 3¹²³⁴⁵+127 -> $num { start $num.is-prime ?? "$num is prime" !! "$num is not prime";; } CATCH { .backtrace.full.say } And that backtrace

[perl #129088] [BUG] Error message provokes panic

2016-08-31 Thread jn...@jnthn.net via RT
On Sun Aug 28 10:16:31 2016, 1parr...@gmail.com wrote: > > I think you're getting an end user's-eye view of what internal > > backtraces look like. > > Right! If the problem is simply a user error, (an invalid entry in an > sprintf format string), the messages are irrelevant and confusing. > > I

Re: [perl #129120] [CONC] in await: Cannot invoke this object (REPR: Null; VMNull)

2016-08-31 Thread Nicholas Clark
On Wed, Aug 31, 2016 at 02:58:50AM -0700, jn...@jnthn.net via RT wrote: > On Sun Aug 28 20:09:29 2016, c...@zoffix.com wrote: > > On occasion, I get this error when trying to run the bellow program on > > a 32-core box: > > > > $ time RAKUDO_MAX_THREADS=40 perl6 foo.p6 > > Cannot invoke this objec

[perl #129120] [CONC] in await: Cannot invoke this object (REPR: Null; VMNull)

2016-08-31 Thread jn...@jnthn.net via RT
On Sun Aug 28 20:09:29 2016, c...@zoffix.com wrote: > On occasion, I get this error when trying to run the bellow program on > a 32-core box: > > $ time RAKUDO_MAX_THREADS=40 perl6 foo.p6 > Cannot invoke this object (REPR: Null; VMNull) > in block at foo.p6 line 9 > > > sub what-is { > ret

[perl #129150] [RFC][BUG] IO::Notification needs .stat and seperate notification for removal

2016-08-31 Thread via RT
# New Ticket Created by 刘刊 # Please include the string: [perl #129150] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=129150 > Two scenarios will render the following code "useless". my $p = Promise.new; IO::Notification.watc