Re: [perl #102994] State variables are never initialized if the first call of the containing block does not reach them

2016-08-19 Thread Nicholas Clark
On Fri, Aug 19, 2016 at 11:05:07AM -0700, Will Coleda via RT wrote: > On Sat Nov 05 09:12:36 2011, moritz wrote: > > 16:28 < moritz> perl6: sub f($x) { return if $x == 1; state %h = a => 1; > > say > > %h.perl }; f 1; f 2; > > 16:28 <+p6eval> niecza v11-20-gb962c2f: OUTPUT«{"a" => 1

Re: [perl #128983] Feature request: output errors as JSON

2016-08-19 Thread Claudio
Hi Zoffix, You indeed have a point. More abstraction is always the right answer :). Some generic framework exposing the necessary information is a very elegant solution. WIth two buts: 1. For something as basic and fundamental as simple syntax checking it's preferably -imho- not to ask the user

Re: [perl #128984] Feature request (wontfix?): perl -c executes BEGIN and CHECK blocks

2016-08-19 Thread Claudio
Thank you for the clarification. That means that at the moment, most files (i.e. the ones written in OO) will have a have errors without a BEGIN block (i.e. the use of self). As 'perl6 -c' being for now the *only* way to check the syntax of a code file, the security concerns should not be easily d

Re: [perl #129007] [BUG] Baggy.perl confused by type objects

2016-08-19 Thread Zefram
Additional: it also gets confused by some Pair objects as keys: > (("a b" => "c") => 2).Bag.perl ("a b" => "c"=>2).Bag > (("a b" => "c") => 2).Bag.perl.EVAL.perl Type check failed in assignment; expected Int but got Pair (:c(2)) in block at EVAL_15 line 1 in block at line 1 Invoking Pair.p

[perl #129008] [BUG] Pair.perl confused by some type objects

2016-08-19 Thread via RT
# New Ticket Created by Zefram # Please include the string: [perl #129008] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=129008 > Pair.perl produces incorrect output for some type objects: > ((Int) => 2).perl Int => 2 > ((In

[perl #129007] [BUG] Baggy.perl confused by type objects

2016-08-19 Thread via RT
# New Ticket Created by Zefram # Please include the string: [perl #129007] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=129007 > > ((Nil) => 2).Bag.perl (Nil=>2).Bag > ((Nil) => 2).Bag.perl.EVAL.perl ("Nil"=>2).Bag .perl.EV

[perl #129006] [BUG] typed Array .perl doesn't round-trip some iterable elements

2016-08-19 Thread via RT
# New Ticket Created by Zefram # Please include the string: [perl #129006] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=129006 > > Array[Mu].new($((1,2).Seq)).perl Array[Mu].new((1, 2).Seq) > Array[Mu].new($((1,2).Seq)).perl

[perl #129005] [BUG] :D constraint doesn't work when named

2016-08-19 Thread via RT
# New Ticket Created by Zefram # Please include the string: [perl #129005] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=129005 > > constant IntD := Int:D; say IntD.ACCEPTS(Int); say (sub (IntD $a) { $a })(Int) False (Int) O

[perl #129002] [BUG] === confused by subclassed NaN

2016-08-19 Thread via RT
# New Ticket Created by Zefram # Please include the string: [perl #129002] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=129002 > I can vacuously subclass Num and instantiate my new class with specific floating-point values,

[perl #129001] IO::Handle needs printf method

2016-08-19 Thread via RT
# New Ticket Created by Tom Browder # Please include the string: [perl #129001] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=129001 > Most users probably expect to be able to use printf on a file handle.

Re: [perl #128820] [BUG] == on Num literals produces bogus answer

2016-08-19 Thread Zefram
Additional: this also happens with Complex literals, where the real or imaginary parts suffer this as Nums. -zefram

Re: [perl #128817] [BUG] Num.perl doesn't round-trip numeric value

2016-08-19 Thread Zefram
Additional: the same problem arises with Complex.perl, where the real or imaginary parts suffer this problem as Nums. Fixing this for Num won't automatically fix it for Complex, because Complex.perl doesn't invoke Num.perl. -zefram

Re: [perl #128819] [BUG] Num.WHICH doesn't discriminate enough

2016-08-19 Thread Zefram
Additional: the same problem arises with Complex.WHICH, in cases where the real or imaginary parts suffer this problem as Nums. -zefram

[perl #128999] [BUG] === on Num and Complex doesn't distinguish signed zeroes

2016-08-19 Thread via RT
# New Ticket Created by Zefram # Please include the string: [perl #128999] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=128999 > > (0e0).WHICH Num|0 > (-0e0).WHICH Num|-0 > 0e0 === -0e0 True These two Num values are distinc

[perl #126979] [BUG] Infinite loop on 'my @a[;];'

2016-08-19 Thread Will Coleda via RT
On Fri Aug 19 10:54:53 2016, coke wrote: > On Mon Dec 21 06:11:11 2015, andrew.stan...@smoothwall.net wrote: > > Hi > > > > This statement causes an infinite loop in REPL > > my @a[;]; > > > > This is Rakudo version 2015.11-706-g8622b90 built on MoarVM version > > 2015.11-113-gbd56e2e > > imp

[perl #102994] State variables are never initialized if the first call of the containing block does not reach them

2016-08-19 Thread Will Coleda via RT
On Sat Nov 05 09:12:36 2011, moritz wrote: > 16:28 < moritz> perl6: sub f($x) { return if $x == 1; state %h = a => 1; > say > %h.perl }; f 1; f 2; > 16:28 <+p6eval> niecza v11-20-gb962c2f: OUTPUT«{"a" => 1}.hash␤» > 16:28 <+p6eval> ..pugs b927740: OUTPUT«{("a" => 1),}␤» > 16:28 <+p6

[perl #126979] [BUG] Infinite loop on 'my @a[;];'

2016-08-19 Thread Will Coleda via RT
On Mon Dec 21 06:11:11 2015, andrew.stan...@smoothwall.net wrote: > Hi > > This statement causes an infinite loop in REPL > my @a[;]; > > This is Rakudo version 2015.11-706-g8622b90 built on MoarVM version > 2015.11-113-gbd56e2e > implementing Perl 6.b. > > Running on Debian8. > > Also re

[perl #125628] x and xx operators are too different

2016-08-19 Thread Will Coleda via RT
On Sat Jul 18 09:58:45 2015, elizabeth wrote: > Fixed the “a” x Inf case with 059dac9f0be8c563f1a, tests needed > > Did *not* fix the “a” x *, as per discussion at: > http://irclog.perlgeek.de/perl6/2015-07-18#i_10918034 > > > On 16 Jul 2015, at 12:59, Alex Jakimenko (via RT) > follo...@perl.o

[perl #124219] [BUG] Potential missing error text

2016-08-19 Thread Will Coleda via RT
On Tue Mar 31 12:50:50 2015, drf...@pobox.com wrote: > OS: Ubuntu Linux 14.04 LTS in VirtualBox > Host: Windows 8 > Rakudo version: git pull from 25/3/2015 > > Issue 1: Are we missing the line: > > --> token TOP { ⏏ % \n } > > in the error message? > > Issue 2: Should the quantifier be re

[perl #128992] [SEGV] when running S17-procasync/no-runaway-file-limit.t

2016-08-19 Thread via RT
# New Ticket Created by Zoffix Znet # Please include the string: [perl #128992] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=128992 > The previous day I ran make stresstest a ton of times and never had this failure. Today,

[perl #128991] [CONC] Apparent race condition with `done` and ultra-short Supply.interval

2016-08-19 Thread via RT
# New Ticket Created by Zoffix Znet # Please include the string: [perl #128991] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=128991 > This code produces the following exception with Rakudo dd5c28. If interval is changed to