[perl #129889] [BUG] Constraint type check failed for Array parameter

# New Ticket Created by # Please include the string: [perl #129889] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=129889 > This works OK (copied from https://docs.perl6.org/language/list#Typing): perl6 -e 'sub mean(Int

Announce: Rakudo Perl 6 compiler, Release #104 (2016.10)

# Announce: Rakudo Perl 6 compiler, Release #104 (2016.10) On behalf of the Rakudo development team, I’m very happy to announce the October 2016 release of Rakudo Perl 6 #104. Rakudo is an implementation of Perl 6 on the Moar Virtual Machine[^1]. This release implements the 6.c version of the

Re: [perl #129884] Strange behaviour on "say".

On Sat, Oct 15, 2016 at 09:59:01PM +0200, Timo Paulssen wrote: : Actually, I just tested the code and on my machine it always outputs : "test". The only difference between uncommenting "say 'run'" is that : it'll output "run" once at the end - or not. : : So now I'm wondering what i did

Re: [perl #129884] Strange behaviour on "say".

On Sat, Oct 15, 2016 at 09:59:01PM +0200, Timo Paulssen wrote: : Actually, I just tested the code and on my machine it always outputs : "test". The only difference between uncommenting "say 'run'" is that : it'll output "run" once at the end - or not. : : So now I'm wondering what i did

Re: [perl #129884] Strange behaviour on "say".

Actually, I just tested the code and on my machine it always outputs "test". The only difference between uncommenting "say 'run'" is that it'll output "run" once at the end - or not. So now I'm wondering what i did differently from you?!

Re: [perl #129884] Strange behaviour on "say".

On 10/15/2016 01:26 PM, janko popov (via RT) wrote: > # New Ticket Created by janko popov > # Please include the string: [perl #129884] > # in the subject line of all future correspondence about this issue. > # https://rt.perl.org/Ticket/Display.html?id=129884 > > > > Hi, > > Maybe this is

Re: [perl #129884] Strange behaviour on "say".

A clue, for what it's worth. Any valid instruction, (or even a variable declaration) after the "}" ending the innermost loop appears to enable the output. Inside the loop, it doesn't.. On 10/15/16, janko popov wrote: > # New Ticket Created by janko popov > #

[perl #129884] Strange behaviour on "say".

# New Ticket Created by janko popov # Please include the string: [perl #129884] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=129884 > Hi, Maybe this is known bug, maybe not :-) But I cannot finding it on

C static analysis on rakudo sources

Dear all, I've had access to a of C/C++ static analysis tool PVS Studio, and ran it against the latest rakudo sources [1]. The majority of notes seems to be noise, but there were found some valid concerns (or at least looking valid to me) f.ex. this: MoarVM/3rdparty/dynasm/dasm_x86.h:125

[perl #129278] [BUG] Can't assign to `int` private attribute using signature

For the records: This fails on JVM (has to be fixed in src/vm/jvm/runtime/org/perl6/rakudo/Binder.java, probabaly): $ ./perl6-j -e 'class { has int $!n = 0; method x ($!n) {} }.new.x: 42' org.perl6.nqp.sixmodel.reprs.P6OpaqueBaseInstance$BadReferenceRuntimeException: Cannot access a native