[perl #128880] [BUG] Dead code in HyperWhatever, ｢.new｣ is not supposed to work but it does (HyperWhatever.new)

On Tue, 09 Aug 2016 15:25:11 -0700, alex.jakime...@gmail.com wrote: > Let's look at the code in Rakudo! From src/core/Whatever.pm > > my class HyperWhatever { > multi method new(HyperWhatever:) { X::Cannot::New.new(class => > self).throw } > … > } > > So it seems like it should throw a warning

[perl #132846] [Bug] Directive d not applicable for type Int

On Sat, 10 Feb 2018 11:38:50 -0800, juhimar...@gmail.com wrote: > Hi, > > When an Int variable gets undefined, lets say $i, then $i.fmt('%d') > throws a message 'Directive d not applicable for type Int'. > > The message is not ok because %d is applicable! %f throws the same error > but %s does

[perl #132846] [Bug] Directive d not applicable for type Int

On Sat, 10 Feb 2018 11:38:50 -0800, juhimar...@gmail.com wrote: > Hi, > > When an Int variable gets undefined, lets say $i, then $i.fmt('%d') > throws a message 'Directive d not applicable for type Int'. > > The message is not ok because %d is applicable! %f throws the same error > but %s does

[perl #105872] [BUG] 42, 44, 22 -> *@a { say @a.perl }

On Sat, 10 Dec 2011 18:37:03 -0800, jimmy.z...@gmail.com wrote: > JimmyZ> nom: if 42 -> *@_ { say @_.perl } > p6eval> nom 1f9310: OUTPUT«Array.new()␤» > > JimmyZ> niecza: if 42, 44, 22 -> *@a { say @a.perl } > p6eval> niecza v12-10-ga8ad0e9: OUTPUT«(42, 44, 22)␤» > > JimmyZ>nom: if 42, 44, 22 ->

[perl #105872] [BUG] 42, 44, 22 -> *@a { say @a.perl }

On Sat, 10 Dec 2011 18:37:03 -0800, jimmy.z...@gmail.com wrote: > JimmyZ> nom: if 42 -> *@_ { say @_.perl } > p6eval> nom 1f9310: OUTPUT«Array.new()␤» > > JimmyZ> niecza: if 42, 44, 22 -> *@a { say @a.perl } > p6eval> niecza v12-10-ga8ad0e9: OUTPUT«(42, 44, 22)␤» > > JimmyZ>nom: if 42, 44, 22 ->

[perl #131496] [BUG] Failure.perl doesn't roundrip `handled` flag

On Sat, 03 Jun 2017 04:35:14 -0700, c...@zoffix.com wrote: > Handled Failures are explosive again, if they're .perl'ed: > > m: given Failure.new { .so; .handled.say; > .perl.EVAL.handled.say } > rakudo-moar 61ecfd: OUTPUT: «True␤False␤» > > Perhaps the `handled` flag should be a public

[perl #131496] [BUG] Failure.perl doesn't roundrip `handled` flag

On Sat, 03 Jun 2017 04:35:14 -0700, c...@zoffix.com wrote: > Handled Failures are explosive again, if they're .perl'ed: > > m: given Failure.new { .so; .handled.say; > .perl.EVAL.handled.say } > rakudo-moar 61ecfd: OUTPUT: «True␤False␤» > > Perhaps the `handled` flag should be a public

[perl #131617] [BUG] Any.tail(Callable) violates Iterator protocol

On Wed, 21 Jun 2017 11:46:46 -0700, c...@zoffix.com wrote: > The "Died" message should never occur: > > m: my $s = Seq.new: class :: does Iterator { has @!stuff = ; > has $!ded = 1; method pull-one { $!ded or die; @!stuff ?? shift > @!stuff !! $!ded-- && IterationEnd } }.new; say $s.tail: *-10 >

[perl #131617] [BUG] Any.tail(Callable) violates Iterator protocol

On Wed, 21 Jun 2017 11:46:46 -0700, c...@zoffix.com wrote: > The "Died" message should never occur: > > m: my $s = Seq.new: class :: does Iterator { has @!stuff = ; > has $!ded = 1; method pull-one { $!ded or die; @!stuff ?? shift > @!stuff !! $!ded-- && IterationEnd } }.new; say $s.tail: *-10 >

[perl #130431] [REGRESSION] Subclassing an Int no longer works flawlessly (my Foo $a .= new(42))

On Thu, 29 Dec 2016 19:26:07 -0800, alex.jakime...@gmail.com wrote: > Another case: > > class MyInt is Int { method even(){ self %% 2 } }; say [1..4].map({ > MyInt.new($_) }).grep({.even}) > > > Seems like it is a common thing to try, but I'm not going to say that > it should > work. Maybe it

[perl #130431] [REGRESSION] Subclassing an Int no longer works flawlessly (my Foo $a .= new(42))

On Thu, 29 Dec 2016 19:26:07 -0800, alex.jakime...@gmail.com wrote: > Another case: > > class MyInt is Int { method even(){ self %% 2 } }; say [1..4].map({ > MyInt.new($_) }).grep({.even}) > > > Seems like it is a common thing to try, but I'm not going to say that > it should > work. Maybe it

[perl #130748] [BUG] weird error when accessing an attribute from a "where" of another attribute

On Wed, 08 Feb 2017 17:04:56 -0800, fernandocor...@gmail.com wrote: > I’m getting a "VMNull type object” error when I try to access an > attribute from the “where” of another attribute. > > https://irclog.perlgeek.de/perl6/2017-02-09#i_14068796 > > > Fernando Corrêa de Oliveira m: class C {

[perl #130748] [BUG] weird error when accessing an attribute from a "where" of another attribute

On Wed, 08 Feb 2017 17:04:56 -0800, fernandocor...@gmail.com wrote: > I’m getting a "VMNull type object” error when I try to access an > attribute from the “where” of another attribute. > > https://irclog.perlgeek.de/perl6/2017-02-09#i_14068796 > > > Fernando Corrêa de Oliveira m: class C {

[perl #132835] "An operation first awaited" error needs to be clearer

# New Ticket Created by David E. # Please include the string: [perl #132835] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132835 > I've wasted more time than I should've the past few days trying to understand what this

[perl #126703] Typed Shaped Arrays can't be initialized

On Sat, 21 Nov 2015 06:48:27 -0800, timo wrote: > Reproducing test: > > my @a[3;3] = , , ; say @a; # works > my Str @a[3;3] = , , ; say @a; # fails > > 153852 jnthn │ m: say ((0 xx 10) xx 10).WHAT > 153852 +camelia │ rakudo-moar : OUTPUT«(List)␤» > 153857 jnthn │ Curious... > 153933

[perl #126312] [BUG] `for @a` is not creating containers for uninitialized elements

On Sat, 07 May 2016 13:26:09 -0700, sml...@gmail.com wrote: > Confirmed on current Rakudo. > > Interestingly, it works if `for @a` is replaced with `for @a[*]`: > > ➜ my Int @a; @a[5] = 42; $_ = 100 for @a[*]; say @a; > [100 100 100 100 100 100] Seems to have been fixed with Rakudo

[perl #129114] [BUG] state variable declared inside of a {} interpolation in a string, attaches to wrong scope

Just to clarify, the last snippet now produces 0 0 0 0, which is indeed correct. There are tests for this change in general, but possibly not for that particular case. Can we get it covered just in case? ｢testneeded｣ On 2018-02-06 05:51:23, jan-olof.hen...@bredband.net wrote: > On Sun, 28 Aug

[perl #129114] [BUG] state variable declared inside of a {} interpolation in a string, attaches to wrong scope

On Sun, 28 Aug 2016 02:56:47 -0700, sml...@gmail.com wrote: > This is how a state variable normally works: > > ➜ for ^2 { for ^2 { say (state $a)++ } } > 0 > 1 > 0 > 1 > > But when it is declared inside a {} interpolation in a string, it > misbehaves: > > ➜ for ^2 { for ^2 { say "{ (state

[perl #125555] [NYI] Comparison ops for DateTimes in Rakudo

Tests added in https://github.com/perl6/roast/commit/ff0472adfc

[perl #130859] [WEIRD] WhateverCode subscript inside WhateverCode inside block doesn't properly close over lexical

On Sat, 25 Feb 2017 06:55:02 -0800, sml...@gmail.com wrote: > A WhateverCode containing an array subscript that is itself a > WhateverCode, usually works fine... e.g. `*.[*-1]` always returns the > last positional element of its argument. > > A WhateverCode closing over a lexical variable usually

[perl #130859] [WEIRD] WhateverCode subscript inside WhateverCode inside block doesn't properly close over lexical

On Sat, 25 Feb 2017 06:55:02 -0800, sml...@gmail.com wrote: > A WhateverCode containing an array subscript that is itself a > WhateverCode, usually works fine... e.g. `*.[*-1]` always returns the > last positional element of its argument. > > A WhateverCode closing over a lexical variable usually

[perl #128859] [BUG] WhateverCode in a chained comparison fails to parse ("QAST::Block with cuid 1 has not appeared")

On Mon, 02 Oct 2017 22:24:32 -0700, allber...@gmail.com wrote: > [03 05:10:36] m: subset MyStr of Str where 4 < *.chars < > 10; my MyStr $s = 's'; > [03 05:10:37] rakudo-moar fcbd8a: OUTPUT: «===SORRY!===␤ > [03 05:10:37] QAST::Block with cuid 1 has not appeared␤ > [03 05:10:37] » > [03

[perl #128859] [BUG] WhateverCode in a chained comparison fails to parse ("QAST::Block with cuid 1 has not appeared")

On Mon, 02 Oct 2017 22:24:32 -0700, allber...@gmail.com wrote: > [03 05:10:36] m: subset MyStr of Str where 4 < *.chars < > 10; my MyStr $s = 's'; > [03 05:10:37] rakudo-moar fcbd8a: OUTPUT: «===SORRY!===␤ > [03 05:10:37] QAST::Block with cuid 1 has not appeared␤ > [03 05:10:37] » > [03

[perl #131813] Segfault with --profile

Actually, I've been trying to reproduce it on the said revision with --profile, --ll-exception and whatnot, and I can't. I think this is an issue on OS X and therefore should be confirmed (and tested) on OS X also. On 2018-01-06 12:59:07, jan-olof.hen...@bredband.net wrote: > On Fri, 28 Jul 2017

[perl #132328] [SEGV][REGRESSION] DBIish tests are failing spectacularly (JIT compilation of native calls)

Honestly, I have no idea how to test this… maybe someone should attempt to golf it, but given that the commit description is “JIT compile native calls”, I guess it'd be a bit complicated. … I'm fine with just delegating it to the DBIish test suite… On 2017-10-20 08:12:41,

[perl #129787] [CONC] die/CATCH inside a start-block with a channel heisenbugs

FWIW, this bug is somewhat similar in feel: https://github.com/rakudo/rakudo/issues/1202 On 2017-10-15 03:14:02, c...@zoffix.com wrote: > On Wed, 02 Nov 2016 07:13:26 -0700, jn...@jnthn.net wrote: > > On Sun Oct 02 12:52:45 2016, gfldex wrote: > > > sub f(){ > > > my $c = Channel.new; > > > > > >

[perl #112986] [REPL] error 'Use of uninitialized $_ of type Any in numeric context" throws extra errors

 Test in https://github.com/rakudo/rakudo/commit/4385e3fc0b5272a14c1c507ccf5846684c16453a On 2017-08-28 13:58:57, alex.jakime...@gmail.com wrote: > Currently it says this: > Use of uninitialized value of type Any in numeric context > in block at line 1 > > As well as complains about sink

[perl #125299] [BUG] LTA error message when forgetting to close block inside string in Rakudo

Tests here: https://github.com/perl6/roast/commit/2dd5ee1b5935fce03eb815f8336ed26e019d4413 Resolved. Further discussion on https://github.com/rakudo/rakudo/issues/1475 On 2017-12-02 14:39:07, alex.jakime...@gmail.com wrote: > https://irclog.perlgeek.de/perl6/2017-12-02#i_15524141 > > Marking as

[perl #125985] [BUG] Internal error when a constant, unspace, and a map are involved in Rakudo

Anyway, tests in https://github.com/perl6/roast/commit/7557eef426fa4ea102d2d89b84c47dd5c1d3ab08 On 2018-02-03 14:40:09, alex.jakime...@gmail.com wrote: > Ouch. It seems that one of my links is wrong, should've been this one > I think: >

[perl #125985] [BUG] Internal error when a constant, unspace, and a map are involved in Rakudo

Ouch. It seems that one of my links is wrong, should've been this one I think: https://gist.github.com/Whateverable/cedc8ef783acc22e8f07afa98f5ad7d6 On 2017-12-02 19:41:52, alex.jakime...@gmail.com wrote: > Not sure how it golfs down to that, because it never produced the same > error > message.

[perl #130261] [LTA] Error message for unclosed curly quote points to the last line of the file

Tests in https://github.com/perl6/roast/commit/ceabda6337364b5f1cec3c1c5bcb89787f9bcedf On 2018-01-08 15:18:46, alex.jakime...@gmail.com wrote: > Note that the error message is still LTA (says “corresponding starter” > instead > of mentioning “’”), for further progress see RT#125641. > > On

[perl #129296] Splitting non-binary handles no longer works (run(:out, "ls").out.split: 0.chr)

 Tests in https://github.com/perl6/roast/commit/3ca315596c3283c8cd168428065f01062c4633a5 On 2016-11-18 10:51:38, alex.jakime...@gmail.com wrote: > On 2016-11-18 10:38:48, coke wrote: > > On Sun, 18 Sep 2016 03:14:30 -0700, elizabeth wrote: > > > Fixed by reverting 1a03efe4e3b61a07b7df5 in

[perl #127100] [LTA] error message when specifying return type before parameters ( --> Bool, Int $x, Int $y )

Tests in https://github.com/perl6/roast/commit/3dab7c774587fbf8ae2afb561b02b3177659ace3 On 2017-10-07 15:55:27, alex.jakime...@gmail.com wrote: > This was resolved in these commits: > * > https://github.com/rakudo/rakudo/commit/ac97a4016196c1fb5c39365dfbe8980574fb929b > * >

[perl #127671] [EXOTICTEST] ｢dir｣ dies if weird unicode sequences are encountered (dir;)

Test added in https://github.com/perl6/roast/commit/a7590d6543e1d29bc935377c727e4d15e38ee713 Note that the test *does create* files with weird names, but that's totally OK in /tmp I think. On 2017-03-02 07:06:54, c...@zoffix.com wrote: > Explanation and ideas on IRC:

[perl #129882] [TESTNEEDED] [CONC] [IO] Proc with `.in.close` and `.out.slurp-rest` in different threads, hangs

Test in https://github.com/perl6/roast/commit/195227f779f7441de1678e12941550271da799b2 On 2017-07-09 19:40:57, alex.jakime...@gmail.com wrote: > That's pretty good. But issues are not closed without tests, unless > there's a > good reason not to add a test. No reason was mentioned, therefore >

[perl #125674] [LTA] error message prints wrong eject position (if True if { };)

Does not seem to be fixed at all. But I've added some todo-ed tests: https://github.com/perl6/roast/commit/f9f5034a1e66e068bfe21227e35f100f3c1e3fef On 2017-10-07 13:43:30, alex.jakime...@gmail.com wrote: > Should be fixed in https://github.com/rakudo/rakudo/commit/5747bc7121 > > Testneeded.

[perl #123776] Binding a variable at BEGIN time doesn't stick aruond for runtime

On Tue, 30 Jan 2018 19:03:13 -0800, c...@zoffix.com wrote: > On Tue, 30 Jan 2018 15:08:38 -0800, c...@zoffix.com wrote: > > On Fri, 01 Dec 2017 12:09:05 -0800, alex.jakime...@gmail.com wrote: > > > Still reproducible (2017.11, HEAD(5929887)), but is supposed to > > > work? > > > > Don't see any

[perl #131409] whatever auto closure fails with smartmatch with regex

On Wed, 31 May 2017 03:31:49 -0700, zengargo...@gmail.com wrote: > When using smartmatch against a regex, auto-whatever closure generation > does not work whereas manual pointy closure does work. > > A '{ * eq $match}' behaves differently than a '{ * ~~ /<$match>/}'. > However, '-> $x { $x ~~

[perl #131409] whatever auto closure fails with smartmatch with regex

On Wed, 31 May 2017 03:31:49 -0700, zengargo...@gmail.com wrote: > When using smartmatch against a regex, auto-whatever closure generation > does not work whereas manual pointy closure does work. > > A '{ * eq $match}' behaves differently than a '{ * ~~ /<$match>/}'. > However, '-> $x { $x ~~

[perl #132794] Junction as default value of MAIN param hangs forever

On Wed, 31 Jan 2018 07:56:31 -0800, c...@zoffix.com wrote: > On Wed, 31 Jan 2018 07:26:24 -0800, pawel.pab...@getresponse.com > wrote: > > $ perl6 -e 'sub MAIN ( $x = 1|2 ) { }' > > > > Following oneliner will hang forever on Rakudo 2018.01. > > Error exists for all type of Junctions. > > Doesn't

[perl #132794] Junction as default value of MAIN param hangs forever

On Wed, 31 Jan 2018 07:56:31 -0800, c...@zoffix.com wrote: > On Wed, 31 Jan 2018 07:26:24 -0800, pawel.pab...@getresponse.com > wrote: > > $ perl6 -e 'sub MAIN ( $x = 1|2 ) { }' > > > > Following oneliner will hang forever on Rakudo 2018.01. > > Error exists for all type of Junctions. > > Doesn't

[perl #132794] Junction as default value of MAIN param hangs forever

On Wed, 31 Jan 2018 07:26:24 -0800, pawel.pab...@getresponse.com wrote: > $ perl6 -e 'sub MAIN ( $x = 1|2 ) { }' > > Following oneliner will hang forever on Rakudo 2018.01. > Error exists for all type of Junctions. > Doesn't matter if they are built by infix "1|2" or by method "any(1,2)". We can

[perl #132794] Junction as default value of MAIN param hangs forever

On Wed, 31 Jan 2018 07:26:24 -0800, pawel.pab...@getresponse.com wrote: > $ perl6 -e 'sub MAIN ( $x = 1|2 ) { }' > > Following oneliner will hang forever on Rakudo 2018.01. > Error exists for all type of Junctions. > Doesn't matter if they are built by infix "1|2" or by method "any(1,2)". We can

[perl #132794] Junction as default value of MAIN param hangs forever

# New Ticket Created by Paweł Pabian # Please include the string: [perl #132794] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132794 > $ perl6 -e 'sub MAIN ( $x = 1|2 ) { }' Following oneliner will hang forever on Rakudo

[perl #123776] Binding a variable at BEGIN time doesn't stick aruond for runtime

On Tue, 30 Jan 2018 15:08:38 -0800, c...@zoffix.com wrote: > On Fri, 01 Dec 2017 12:09:05 -0800, alex.jakime...@gmail.com wrote: > > Still reproducible (2017.11, HEAD(5929887)), but is supposed to work? > > Don't see any reason why that'd be questionable. > > > On 2015-02-09 17:43:52,

[perl #123776] Binding a variable at BEGIN time doesn't stick aruond for runtime

On Tue, 30 Jan 2018 15:08:38 -0800, c...@zoffix.com wrote: > On Fri, 01 Dec 2017 12:09:05 -0800, alex.jakime...@gmail.com wrote: > > Still reproducible (2017.11, HEAD(5929887)), but is supposed to work? > > Don't see any reason why that'd be questionable. > > > On 2015-02-09 17:43:52,

[perl #123776] [@LARRY] Binding a variable at BEGIN time doesn't stick aruond for runtime

On Fri, 01 Dec 2017 12:09:05 -0800, alex.jakime...@gmail.com wrote: > Still reproducible (2017.11, HEAD(5929887)), but is supposed to work? Don't see any reason why that'd be questionable. > On 2015-02-09 17:43:52, rayd...@cyberuniverses.com wrote: > > m: my $a; BEGIN { $a := 1; say $a; }; say

[perl #123776] [@LARRY] Binding a variable at BEGIN time doesn't stick aruond for runtime

On Fri, 01 Dec 2017 12:09:05 -0800, alex.jakime...@gmail.com wrote: > Still reproducible (2017.11, HEAD(5929887)), but is supposed to work? Don't see any reason why that'd be questionable. > On 2015-02-09 17:43:52, rayd...@cyberuniverses.com wrote: > > m: my $a; BEGIN { $a := 1; say $a; }; say

[perl #127226] QUOTE does not remove backslash with adverb :b

On Fri, 23 Jun 2017 05:28:22 -0700, c...@zoffix.com wrote: > On Sat, 09 Jan 2016 10:23:18 -0800, gfldex wrote: > > my $x = 42; say Q:s:b{\$x} > > > > # OUTPUT«\42␤» > > # EXPECTED«42␤» > > Worth nothing the OP's expected is not correct. The result should be > string '$x', as the backslash would

[perl #127226] QUOTE does not remove backslash with adverb :b

On Fri, 23 Jun 2017 05:28:22 -0700, c...@zoffix.com wrote: > On Sat, 09 Jan 2016 10:23:18 -0800, gfldex wrote: > > my $x = 42; say Q:s:b{\$x} > > > > # OUTPUT«\42␤» > > # EXPECTED«42␤» > > Worth nothing the OP's expected is not correct. The result should be > string '$x', as the backslash would

[perl #132780] Issue with one and none Junctins when passed as parameter

Thank you for the report. On Sun, 28 Jan 2018 21:40:35 -0800, shinobi...@gmail.com wrote: > I need the junction to be applied inside the regex, not at time of > parameter binding, so i use the type Mu. This part I explained last night on IRC:

[perl #132780] Issue with one and none Junctins when passed as parameter

Thank you for the report. On Sun, 28 Jan 2018 21:40:35 -0800, shinobi...@gmail.com wrote: > I need the junction to be applied inside the regex, not at time of > parameter binding, so i use the type Mu. This part I explained last night on IRC:

[perl #130485] [SEVERE] » is no longer shuffled (».say)

On Sat, 07 Oct 2017 09:38:10 -0700, alex.jakime...@gmail.com wrote: > » is supposed to be an explicit promise that you don't care > about > order, and there are lots of places that are not marked pure that are > nevertheless effectively pure > > On 2017-10-07 09:34:59, alex.jakime...@gmail.com

[perl #130485] [SEVERE] » is no longer shuffled (».say)

On Sat, 07 Oct 2017 09:38:10 -0700, alex.jakime...@gmail.com wrote: > » is supposed to be an explicit promise that you don't care > about > order, and there are lots of places that are not marked pure that are > nevertheless effectively pure > > On 2017-10-07 09:34:59, alex.jakime...@gmail.com

[perl #129801] [LTA] Nesting LEAVE and ENTER phasers says "Cannot reference undeclared local 'enter_result__1"

On Mon, 03 Oct 2016 11:59:18 -0700, sml...@gmail.com wrote: > I tried to time a subroutine as follows: > > ➜ sub a { LEAVE say now - ENTER now; sleep 1 }; > ➜ a > ===SORRY!=== > Cannot reference undeclared local 'enter_result__1 > > Not sure if nesting phasers like this would

[perl #129801] [LTA] Nesting LEAVE and ENTER phasers says "Cannot reference undeclared local 'enter_result__1"

On Mon, 03 Oct 2016 11:59:18 -0700, sml...@gmail.com wrote: > I tried to time a subroutine as follows: > > ➜ sub a { LEAVE say now - ENTER now; sleep 1 }; > ➜ a > ===SORRY!=== > Cannot reference undeclared local 'enter_result__1 > > Not sure if nesting phasers like this would

[perl #127135] [BUG] Infinite Loop with missing second arg on .subst-mutate

On Mon, 04 Jan 2016 03:00:00 -0800, elizabeth wrote: > > On 04 Jan 2016, at 11:51, Lloyd Fournier > > wrote: > > > > There is no mention of subst-mutate in the design docs. Should I > > still write tests in roast? > > Well, subst-mutate is *not* used inside of the core

[perl #127135] [BUG] Infinite Loop with missing second arg on .subst-mutate

On Mon, 04 Jan 2016 03:00:00 -0800, elizabeth wrote: > > On 04 Jan 2016, at 11:51, Lloyd Fournier > > wrote: > > > > There is no mention of subst-mutate in the design docs. Should I > > still write tests in roast? > > Well, subst-mutate is *not* used inside of the core

[perl #130532] [JVM] Failing tests for itemization of arguments with infix: after introduction of Rakudo::Internals.OneValueIterator

On Sat, 14 Jan 2017 13:46:47 -0800, barto...@gmx.de wrote: > On Tue, 10 Jan 2017 12:46:48 -0800, barto...@gmx.de wrote: > > I managed to golf this a bit: > > > > $ ./perl6-j -e 'use nqp; class A { has Mu $!foo; method bar () { > > $!foo > > := nqp::null; say nqp::isnull($!foo) ?? "null" !! $!foo }

[perl #130532] [JVM] Failing tests for itemization of arguments with infix: after introduction of Rakudo::Internals.OneValueIterator

On Sat, 14 Jan 2017 13:46:47 -0800, barto...@gmx.de wrote: > On Tue, 10 Jan 2017 12:46:48 -0800, barto...@gmx.de wrote: > > I managed to golf this a bit: > > > > $ ./perl6-j -e 'use nqp; class A { has Mu $!foo; method bar () { > > $!foo > > := nqp::null; say nqp::isnull($!foo) ?? "null" !! $!foo }

[perl #126702] [JVM] failing test in S06-multi/subsignature.t: wrong multi candidate called when slurpy and named are passed

On Sat, 21 Nov 2015 06:12:07 -0800, barto...@gmx.de wrote: > The following code does not give the expected result ('2') on > rakudo.jvm: > > $ perl6-j -e 'multi catch(| (*@all ) ) { 1 }; multi catch(| (*@all, > :$really! ) ) { 2 }; say catch(0, 5, :!really)' > 1 Neither the mentioned test file

[perl #132172] [BUG] `orelse` + block in a string gets the wrong $_

On Wed, 27 Sep 2017 07:09:16 -0700, c...@zoffix.com wrote: > Here, instead of the Failure, the $_ is an Any: > > 13:59 m: sub x { my $ver = .lines.uc with "blazr".IO.open > orelse note "meow {.exception.message}" and return 42; "meow$ver" }; > dd x > 13:59 camelia rakudo-moar

[perl #126984] [BUG] WhateverCode in given doesn't get refreshed when entering surrounding block in Rakudo

On Mon, 21 Dec 2015 13:33:51 -0800, masak wrote: > m: sub foo($x) { say (* == $x)($_) given $x }; foo(1); foo(2) > rakudo-moar cfb1f3: OUTPUT«True␤False␤» > * masak submits rakudobug > > Examining the expression printed, it basically says "$x should be > numerically equal to itself" in a

[perl #126984] [BUG] WhateverCode in given doesn't get refreshed when entering surrounding block in Rakudo

On Mon, 21 Dec 2015 13:33:51 -0800, masak wrote: > m: sub foo($x) { say (* == $x)($_) given $x }; foo(1); foo(2) > rakudo-moar cfb1f3: OUTPUT«True␤False␤» > * masak submits rakudobug > > Examining the expression printed, it basically says "$x should be > numerically equal to itself" in a

[perl #128054] [PARSER] In a string enclosed in parens, a {}-interpolation can't access the topic $_ of a statement modifier

On Tue, 03 Oct 2017 09:38:23 -0700, b...@abrij.org wrote: > On Mon, 02 Oct 2017 19:08:27 -0700, alex.jakime...@gmail.com wrote: > > Also worth taking a look at > > https://rt.perl.org/Ticket/Display.html?id=126569 > > > > On 2017-09-29 14:06:58, b...@abrij.org wrote: > > > On Sun, 28 May 2017

[perl #132172] [BUG] `orelse` + block in a string gets the wrong $_

On Wed, 27 Sep 2017 07:09:16 -0700, c...@zoffix.com wrote: > Here, instead of the Failure, the $_ is an Any: > > 13:59 m: sub x { my $ver = .lines.uc with "blazr".IO.open > orelse note "meow {.exception.message}" and return 42; "meow$ver" }; > dd x > 13:59 camelia rakudo-moar

[perl #126413] [BUG] WhateverCode loses topic inside given modifier

On Tue, 20 Oct 2015 18:11:22 -0700, larry wrote: > This works: > > > p6 'given 10 { say (* + $_)(32) }' > 42 > > but this doesn't: > > > p6 'say (* + $_)(32) given 10' > Use of uninitialized value of type Any in numeric context in whatevercode > at -e:1 > 32 Thank you for the report. This is

[perl #126413] [BUG] WhateverCode loses topic inside given modifier

On Tue, 20 Oct 2015 18:11:22 -0700, larry wrote: > This works: > > > p6 'given 10 { say (* + $_)(32) }' > 42 > > but this doesn't: > > > p6 'say (* + $_)(32) given 10' > Use of uninitialized value of type Any in numeric context in whatevercode > at -e:1 > 32 Thank you for the report. This is

[perl #128054] [PARSER] In a string enclosed in parens, a {}-interpolation can't access the topic $_ of a statement modifier

On Tue, 03 Oct 2017 09:38:23 -0700, b...@abrij.org wrote: > On Mon, 02 Oct 2017 19:08:27 -0700, alex.jakime...@gmail.com wrote: > > Also worth taking a look at > > https://rt.perl.org/Ticket/Display.html?id=126569 > > > > On 2017-09-29 14:06:58, b...@abrij.org wrote: > > > On Sun, 28 May 2017

[perl #132211] [BUG] combination of `andthen` and `orelse` causes closed over variable to never update

On Tue, 03 Oct 2017 08:07:41 -0700, c...@zoffix.com wrote: > IRC: https://irclog.perlgeek.de/perl6/2017-10-03#i_15250878 > > Reads "aaa", not "abc": > 15:05 Zoffix m: for { $^v.uc andthen say $v orelse .say } > 15:05 camelia rakudo-moar f946bd: OUTPUT: «a␤a␤a␤» > >

[perl #126569] [BUG] xx-repeated expression enclosed in parens can't access the topic $_ of a statement modifier

On Thu, 05 Nov 2015 01:58:17 -0800, sml...@gmail.com wrote: > This works: > > ➜ .pick xx 10 given 1..6 > (6 3 1 1 5 1 6 3 4 2) > > But putting parens around the xx operation, breaks it: > > ➜ (.pick xx 10) given 1..6 > ((Any) (Any) (Any) (Any) (Any) (Any) (Any) (Any) (Any) (Any)) > > The

[perl #131548] [BUG] andthen weirdness with lexicals

On Fri, 09 Jun 2017 12:48:55 -0700, c...@cpan.org wrote: > Example code: > > $ cat bug.p6 > for ^7 { > my $x = 1; > 1 andthen print "$x " > andthen $x = 2 > andthen $x = 3 > andthen $x = 4; > } > > Output: > > $ perl6 bug.p6 > 1 4 3 3 3 3 3 > > We apparently create a

[perl #130575] [BUG] Variables inside a try {} block used with `andthen` don't always get updated to correct values

On Tue, 17 Jan 2017 10:04:11 -0800, c...@zoffix.com wrote: > m: sub itcavuc ($c) { (try say $c) andthen 42 }; itcavuc $_ > for 2, 4, 6 > rakudo-moar 7d5bbe: OUTPUT«2␤4␤6␤» > m: sub itcavuc ($c) { try {say $c} andthen 42 }; itcavuc $_ > for 2, 4, 6 > rakudo-moar 7d5bbe: OUTPUT«2␤2␤4␤» > > The

[perl #130575] [BUG] Variables inside a try {} block used with `andthen` don't always get updated to correct values

On Tue, 17 Jan 2017 10:04:11 -0800, c...@zoffix.com wrote: > m: sub itcavuc ($c) { (try say $c) andthen 42 }; itcavuc $_ > for 2, 4, 6 > rakudo-moar 7d5bbe: OUTPUT«2␤4␤6␤» > m: sub itcavuc ($c) { try {say $c} andthen 42 }; itcavuc $_ > for 2, 4, 6 > rakudo-moar 7d5bbe: OUTPUT«2␤2␤4␤» > > The

[perl #132211] [BUG] combination of `andthen` and `orelse` causes closed over variable to never update

On Tue, 03 Oct 2017 08:07:41 -0700, c...@zoffix.com wrote: > IRC: https://irclog.perlgeek.de/perl6/2017-10-03#i_15250878 > > Reads "aaa", not "abc": > 15:05 Zoffix m: for { $^v.uc andthen say $v orelse .say } > 15:05 camelia rakudo-moar f946bd: OUTPUT: «a␤a␤a␤» > >

[perl #132337] [BUG] Code block inside `andthen`/`orelse` doesn't close over lexical variables correctly

On Sat, 21 Oct 2017 06:23:40 -0700, sml...@gmail.com wrote: > Golfed example: > > sub foo ($str) { > { say $str }() orelse Nil > } > > foo "aa"; # aa > foo "bb"; # aa > > The second call should print "bb", not "aa". > > Replacing the `say` with `return`, throws

[perl #132337] [BUG] Code block inside `andthen`/`orelse` doesn't close over lexical variables correctly

On Sat, 21 Oct 2017 06:23:40 -0700, sml...@gmail.com wrote: > Golfed example: > > sub foo ($str) { > { say $str }() orelse Nil > } > > foo "aa"; # aa > foo "bb"; # aa > > The second call should print "bb", not "aa". > > Replacing the `say` with `return`, throws

[perl #131548] [BUG] andthen weirdness with lexicals

On Fri, 09 Jun 2017 12:48:55 -0700, c...@cpan.org wrote: > Example code: > > $ cat bug.p6 > for ^7 { > my $x = 1; > 1 andthen print "$x " > andthen $x = 2 > andthen $x = 3 > andthen $x = 4; > } > > Output: > > $ perl6 bug.p6 > 1 4 3 3 3 3 3 > > We apparently create a

[perl #126569] [BUG] xx-repeated expression enclosed in parens can't access the topic $_ of a statement modifier

On Thu, 05 Nov 2015 01:58:17 -0800, sml...@gmail.com wrote: > This works: > > ➜ .pick xx 10 given 1..6 > (6 3 1 1 5 1 6 3 4 2) > > But putting parens around the xx operation, breaks it: > > ➜ (.pick xx 10) given 1..6 > ((Any) (Any) (Any) (Any) (Any) (Any) (Any) (Any) (Any) (Any)) > > The

[perl #132104] [JVM] EvalServer leaks threads and memory when using Proc::Async

On Thu, 12 Oct 2017 13:35:27 -0700, barto...@gmx.de wrote: > On Sat, 23 Sep 2017 12:28:53 -0700, barto...@gmx.de wrote: > > 3) Feeding the EvalServer with a program that calls 'run' (or > > Proc::Async directly) does heavily leak memory, threads and what not > > (again assuming a clean EvalServer

[perl #132104] [JVM] EvalServer leaks threads and memory when using Proc::Async

On Thu, 12 Oct 2017 13:35:27 -0700, barto...@gmx.de wrote: > On Sat, 23 Sep 2017 12:28:53 -0700, barto...@gmx.de wrote: > > 3) Feeding the EvalServer with a program that calls 'run' (or > > Proc::Async directly) does heavily leak memory, threads and what not > > (again assuming a clean EvalServer

[perl #127291] [BUG] temp fails to set hashes with non-string key type constraints

On Sat, 16 Jan 2016 13:33:45 -0800, rightf...@gmail.com wrote: > The following code: > > my %h{Pair}; > %h{a => 1} = 2; > temp %h = %h.clone; > > should succeed. However, it fails with the following error: > > > Type check failed in binding key; expected Pair but got Str > > Rakudo version: >

[perl #127291] [BUG] temp fails to set hashes with non-string key type constraints

On Sat, 16 Jan 2016 13:33:45 -0800, rightf...@gmail.com wrote: > The following code: > > my %h{Pair}; > %h{a => 1} = 2; > temp %h = %h.clone; > > should succeed. However, it fails with the following error: > > > Type check failed in binding key; expected Pair but got Str > > Rakudo version: >

[perl #132742] [BUILD] FreeBSD and OpenBSD Builds now dependent on gmake

This was fixed, for more info see this still-open issue: https://github.com/rakudo/rakudo/issues/1420 On 2018-01-19 07:36:32, steve.myn...@gmail.com wrote: > Both builds are broken see #132741 but I believe the change to make > these builds dependent on gmake isn't neccessary. > > None of the

[perl #132741] [BUILD] Broken on FreeBSD and OpenBSD

This was fixed, for more info see this still-open issue: https://github.com/rakudo/rakudo/issues/1420 On 2018-01-19 07:30:48, steve.myn...@gmail.com wrote: > MoarVM build broken on FreeBSD 11 and OpenBSD 6.2 > > .. > > Configuring and building MoarVM ... > /usr/local/bin/perl5 Configure.pl

[perl #128712] [LTA] quote colon form in identifier lacks line number

On Sat, 23 Jul 2016 16:49:44 -0700, gfldex wrote: > my $i = 42; my $foo:bar«$i»; > # OUTPUT: > #===SORRY!=== > #QAST::Var with scope '' NYI > # > #shell returned 1 Thank you for the report. This is now fixed in branch `post-release`. Note that the variable needs to have compile-time value to be

[perl #128712] [LTA] quote colon form in identifier lacks line number

On Sat, 23 Jul 2016 16:49:44 -0700, gfldex wrote: > my $i = 42; my $foo:bar«$i»; > # OUTPUT: > #===SORRY!=== > #QAST::Var with scope '' NYI > # > #shell returned 1 Thank you for the report. This is now fixed in branch `post-release`. Note that the variable needs to have compile-time value to be

[perl #126296] [BUG] Foo:D type on attribute should imply 'is required' and not need intialiser

On Thu, 08 Oct 2015 03:12:02 -0700, ilmari wrote: > Or to put another way: attributes with 'is required' should not need > an > initialiser even if the type has a :D smiley, and a :D type without an > initialiser should imply 'is required'. > > The first and second examples below should be

[perl #126296] [BUG] Foo:D type on attribute should imply 'is required' and not need intialiser

On Thu, 08 Oct 2015 03:12:02 -0700, ilmari wrote: > Or to put another way: attributes with 'is required' should not need > an > initialiser even if the type has a :D smiley, and a :D type without an > initialiser should imply 'is required'. > > The first and second examples below should be

[perl #130086] [BUG] multiple eof-s support on $*IN

On Sun, 13 Nov 2016 08:07:34 -0800, vivids...@gmail.com wrote: > Hello > > It is expected to be able to pass multiple eof-s (by pressing Ctrl+D). > > working p5 script: multiple-eof.pl > and two variants of p6 scripts, which falls to endless loop after > first "eof". > > Rakudo version 2016.10

[perl #130086] [BUG] multiple eof-s support on $*IN

On Sun, 13 Nov 2016 08:07:34 -0800, vivids...@gmail.com wrote: > Hello > > It is expected to be able to pass multiple eof-s (by pressing Ctrl+D). > > working p5 script: multiple-eof.pl > and two variants of p6 scripts, which falls to endless loop after > first "eof". > > Rakudo version 2016.10

[perl #129790] [OPTIMIZER] Giving a sub to a map fails

On Sat, 14 Oct 2017 18:38:47 -0700, alex.jakime...@gmail.com wrote: > Maybe it is worth noting that this is pretty much a regression (even > though an > old one, and caused by a non-optimizer change). > > (2016-08-09) >

[perl #129790] [OPTIMIZER] Giving a sub to a map fails

On Sat, 14 Oct 2017 18:38:47 -0700, alex.jakime...@gmail.com wrote: > Maybe it is worth noting that this is pretty much a regression (even > though an > old one, and caused by a non-optimizer change). > > (2016-08-09) >

[perl #128935] [BUG] "where" clauses are parsed, but not enforced, in "my" expressions

On Sun, 04 Dec 2016 01:21:56 -0800, c...@zoffix.com wrote: > On Sun, 14 Aug 2016 18:19:44 -0700, timo wrote: > > > > gfldex: m: dd my ($i, $k where * == 4) = (1,3); dd $i, $k > > +camelia: rakudo-moar ee8a25: OUTPUT«(1, 3)␤Int $i = 1␤Int $k = 3␤» > > > > Shouldn't allow $k to be bound to any

[perl #128935] [BUG] "where" clauses are parsed, but not enforced, in "my" expressions

On Sun, 04 Dec 2016 01:21:56 -0800, c...@zoffix.com wrote: > On Sun, 14 Aug 2016 18:19:44 -0700, timo wrote: > > > > gfldex: m: dd my ($i, $k where * == 4) = (1,3); dd $i, $k > > +camelia: rakudo-moar ee8a25: OUTPUT«(1, 3)␤Int $i = 1␤Int $k = 3␤» > > > > Shouldn't allow $k to be bound to any

[perl #128710] combining :D, a where clause and Nil results in empty type object

On Sat, 23 Jul 2016 15:57:33 -0700, gfldex wrote: > sub niler{Nil}; my Int:D $i where .defined = niler(); say $i; say $i.WHAT; > # OUTPUT«()␤()␤» > # expected: well, I don't know since I explicitely asked for a defined > # value _twice_ but Nil is supposed to revert a container to it's default. >

[perl #128710] combining :D, a where clause and Nil results in empty type object

On Sat, 23 Jul 2016 15:57:33 -0700, gfldex wrote: > sub niler{Nil}; my Int:D $i where .defined = niler(); say $i; say $i.WHAT; > # OUTPUT«()␤()␤» > # expected: well, I don't know since I explicitely asked for a defined > # value _twice_ but Nil is supposed to revert a container to it's default. >

[perl #126914] Block less try fails to catch exception

On Mon, 14 Dec 2015 00:48:15 -0800, nadim.khe...@gmail.com wrote: > https://rt.perl.org/Ticket/Display.html?id=126914 > > http://nopaste.linux-dev.org/?881099 > > In this code a 'say' was added to all the subs. the previuosly passing > *_orelse also fails to catch the exception Thanks, but the

[perl #126914] Block less try fails to catch exception

On Mon, 14 Dec 2015 00:48:15 -0800, nadim.khe...@gmail.com wrote: > https://rt.perl.org/Ticket/Display.html?id=126914 > > http://nopaste.linux-dev.org/?881099 > > In this code a 'say' was added to all the subs. the previuosly passing > *_orelse also fails to catch the exception Thanks, but the

[perl #126856] [LTA] No spaces allowed around .^ and .? (^42 .^methods.say)

On Wed, 09 Dec 2015 08:38:16 -0800, alex.jakime...@gmail.com wrote: > Code: > ^42 .^methods.say > > Result: > ===SORRY!=== Error while compiling -e > Unsupported use of . to concatenate strings; in Perl 6 please use ~ > at -e:1 > --> 42.^⏏methods.say > > > Arguably it should work, just

<    1   2   3   4   5   6   7   8   9   10   >