[perl #132085] [REGRESSION] Possible regression after Match.(made|ast) changes

2017-09-13 Thread Aleks-Daniel Jakimenko-Aleksejev via RT
Thanks! On 2017-09-13 21:02:09, lloyd.fo...@gmail.com wrote: > I think we can close this. It's most likely an internals change > because I > call nqp::setparameterizer() directly. I'll figure out what the > problem is > eventually and if I can't fix it myself I'll open a more concise RT. > >

Re: [perl #132085] [REGRESSION] Possible regression after Match.(made|ast) changes

2017-09-13 Thread Lloyd Fournier via RT
I think we can close this. It's most likely an internals change because I call nqp::setparameterizer() directly. I'll figure out what the problem is eventually and if I can't fix it myself I'll open a more concise RT. Cheers LL On Thu, Sep 14, 2017 at 1:27 PM Aleks-Daniel Jakimenko-Aleksejev <

Re: [perl #132085] [REGRESSION] Possible regression after Match.(made|ast) changes

2017-09-13 Thread Lloyd Fournier
I think we can close this. It's most likely an internals change because I call nqp::setparameterizer() directly. I'll figure out what the problem is eventually and if I can't fix it myself I'll open a more concise RT. Cheers LL On Thu, Sep 14, 2017 at 1:27 PM Aleks-Daniel Jakimenko-Aleksejev <

[perl #132085] [REGRESSION] Possible regression after Match.(made|ast) changes

2017-09-13 Thread via RT
# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev # Please include the string: [perl #132085] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132085 > Spit tests are failing on HEAD (https://github.com/spitsh/spitsh).

[perl #131962] [TESTNEEDED] [REGRESSION] `Pair.kv`/`.keys`/.`values` dies if either the key or the value is `Mu`

2017-09-13 Thread Brian S. Julin via RT
On Sat, 26 Aug 2017 06:17:15 -0700, elizabeth wrote: > Fixed with a5014fd0855545cc083b3590 , tests needed. > > > On 26 Aug 2017, at 13:10, Sam S. (via RT) > follo...@perl.org> wrote: > > > > # New Ticket Created by Sam S. > > # Please include the string: [perl #131962] > > # in the subject

[perl #132081] [LTA] Wrong exception type on bad attribute default values

2017-09-13 Thread Brian S. Julin via RT
On Wed, 13 Sep 2017 18:21:56 -0700, b...@abrij.org wrote: > $ perl6 -e 'my Int $a is default("foo");' > ===SORRY!=== Error while compiling -e > Default value 'foo' will never bind to a parameter of type Int > at -e:1 > --> my Int $a is default("foo")⏏; > expecting any of: >

[perl #126318] [BUG] trait 'is default' on attributes has no effect

2017-09-13 Thread Brian S. Julin via RT
On Wed, 13 Sep 2017 19:15:36 -0700, b...@abrij.org wrote: > On Fri, 16 Oct 2015 00:54:21 -0700, larry wrote: > > On Sat Oct 10 08:33:13 2015, FROGGS.de wrote: > > > say class { has Int $.foo is default(0) }.new.foo > > > rakudo-moar 025ec1: OUTPUT«(Int)␤» > > > > > > class Foo { has Int $.foo is

[perl #126318] [BUG][TESTNEEDED] trait 'is default' on attributes has no effect

2017-09-13 Thread Brian S. Julin via RT
On Fri, 16 Oct 2015 00:54:21 -0700, larry wrote: > On Sat Oct 10 08:33:13 2015, FROGGS.de wrote: > > say class { has Int $.foo is default(0) }.new.foo > > rakudo-moar 025ec1: OUTPUT«(Int)␤» > > > > class Foo { has Int $.foo is default(0) }; say Foo.new.foo > > rakudo-moar 025ec1: OUTPUT«(Int)␤» >

[perl #132030] [TESTNEEDED] [REGRESSION] Broken Text::CSV tests and possibly other ecosystem fallout

2017-09-13 Thread Aleks-Daniel Jakimenko-Aleksejev via RT
NCurses, Term::Choose, Term::Choose::Util, and Term::TablePrint: https://github.com/azawawi/perl6-ncurses/issues/16 This one is weird because it seems to be working unless you run it under prove. Perhaps the module is alright but it's the test that is broken. On 2017-09-13 18:16:56,

[perl #131387] [TESTNEEDED] `is default` value not applied to attributes by default

2017-09-13 Thread Brian S. Julin via RT
On Tue, 12 Sep 2017 06:57:13 -0700, jn...@jnthn.net wrote: > On Sat, 27 May 2017 19:35:53 -0700, c...@zoffix.com wrote: > > $z is `Nil` without my having to assign anything, while `$!z` is Any. > > To make `$!z` Nil I also have to assign Nil to it: > > > > m: my $z is default(Nil); dd $z;

[perl #132081] [LTA] Wrong exception type on bad attribute default values

2017-09-13 Thread Brian S. Julin
# New Ticket Created by "Brian S. Julin" # Please include the string: [perl #132081] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132081 > $ perl6 -e 'my Int $a is default("foo");' ===SORRY!=== Error while compiling -e

Re: [perl #129019] [BUG] Range.WHICH fails on many kinds of endpoints

2017-09-13 Thread Zefram
Brian S. Julin via RT wrote: > it would be OK for there to be some tiny chance >of a collision between two WHICH.Str's as long as the actual WHICHs >do not collide. One could make that distinction, but then the .Str of the .WHICH would not fulfill the purposes for which .WHICH

Re: [perl #129019] [BUG] Range.WHICH fails on many kinds of endpoints

2017-09-13 Thread Zefram via RT
Brian S. Julin via RT wrote: > it would be OK for there to be some tiny chance >of a collision between two WHICH.Str's as long as the actual WHICHs >do not collide. One could make that distinction, but then the .Str of the .WHICH would not fulfill the purposes for which .WHICH

[perl #129019] [BUG] Range.WHICH fails on many kinds of endpoints

2017-09-13 Thread Brian S. Julin via RT
On Wed, 30 Aug 2017 07:03:10 -0700, zef...@fysh.org wrote: > Brian S. Julin via RT wrote: > >For example "Foo^".."Bar" and "Foo"^.."Bar" would put out the same WHICH. > > Yes, and that's a bigger problem. In general Rakudo's .WHICH methods > suffer this sort of problem when incorporating the