[perl #125975] [NYI] our \NOW = DateTime.now;

Still NYI (2017.11, HEAD(5929887)) On 2015-09-04 08:25:24, jn...@jnthn.net wrote: > On Thu Sep 03 05:57:58 2015, dakkar wrote: > > Consider this snippet: > > > > constant NOW = DateTime.now; > > > > That is a BEGIN-time declaration + initialisation. C will > > contain > > the time of compilation.

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

https://irclog.perlgeek.de/perl6/2017-12-01#i_15520545 On 2015-06-01 04:26:37, masak wrote: > On Mon Jun 01 01:15:07 2015, FROGGS.de wrote: > > FROGGS: m: say "#={ 42 }" # DrForr: your ticket is invalid > > camelia: rakudo-moar c2a57e: OUTPUT«#=42␤» > > FROGGS: DrForr: I am closing your ticket

[perl #125828] [BUG] Unexpected behavior with `getc` in raw mode

OK, TL;DR you press “q” but nothing happens, and then “q” is received when you press something else. This has been brought up several times, and the reason is that perl 6 works with unicode strings by default (with NFG). It cannot give you “q” right away because there can be a combiner following

[perl #125614] [BUG] Can't store whole 1&2 junctions in Mu-keyed hash in Rakudo

Still reproducible (2017.11, HEAD(5929887)) On 2015-07-14 22:32:47, elizabeth wrote: > > > On 14 Jul 2015, at 12:29, Carl Mäsak (via RT) > follo...@perl.org> wrote: > > > > # New Ticket Created by "Carl Mäsak" > > # Please include the string: [perl #125614] > > # in the subject line of all

[perl #116012] [BUG] What's clearly a postfix is called a prefix in an error message in Rakudo

Still reproducible (2017.11, HEAD(5929887)) The error message is a bit different: ===SORRY!=== Error while compiling -e Variable ':<^^^>' is not declared at -e:1 --> is looser(:<+>) { $a; 77 }; say 6⏏^^^ + 8 On 2015-04-17 03:11:45, FROGGS.de wrote: > This would disallow a too low

[perl #123979] %064b format doesn't deal with negatives

On Fri, 01 Dec 2017 10:57:33 -0800, alex.jakime...@gmail.com wrote: > It is actually fixed now: > > ¦2015.12,b2fbf893db^: > «-1100100» > > ¦b2fbf89,HEAD(5929887): > «-1100100» > >

Re: [perl #126098] [BUG] malformed .perl for Mu but True

Aleks-Daniel Jakimenko-Aleksejev via RT wrote: >tickets wants the thing to be roundtrippable, To preserve the "but" qualifier would be the best outcome, but that's not essential. I'd consider the bug fixed if .perl produced code lacking the "but" but accurately representing everything else. For

Re: [perl #126098] [BUG] malformed .perl for Mu but True

Aleks-Daniel Jakimenko-Aleksejev via RT wrote: >tickets wants the thing to be roundtrippable, To preserve the "but" qualifier would be the best outcome, but that's not essential. I'd consider the bug fixed if .perl produced code lacking the "but" but accurately representing everything else. For

[perl #126098] [BUG] malformed .perl for Mu but True

Still reproducible (2017.11, HEAD(5929887)). However, I'm wondering if it should be fixed at all. If I get it right, the tickets wants the thing to be roundtrippable, but what about cases like: Code: my $a = Mu but role { method blah { 42 } }; say $a.blah; say $a.perl Result: 42

[perl #126142] [NYI] Syntactic Categories in Grammars

Still NYI (2017.11, HEAD(5929887)), but I wonder if we really need it. On 2015-09-23 08:37:57, coke wrote: > See S05-syntactic-categories/new-symbols.t >

[perl #126118] Nil.gist goes missing via type parameter

That's a nice one. Still reproducible (2017.11, HEAD(5929887)) On 2015-09-20 09:29:41, zef...@fysh.org wrote: > $ ./perl6 -e 'sub aa (Mu:U ::T) { say T; my T $a = T; say $a.WHAT; }; > aa(Int); aa(Nil)' > (Int) > (Int) > Nil > Method 'gist' not found for invocant of class 'T' > in sub aa at -e:1 >

[perl #124083] Problem with metaops on num32

This is now fixed: my num32 @arr = 1.1e0,1.2e0,1.3e0; my num32 $s = 0e0; for @arr { $s += $_ }; say $s ¦2015.11,ec18f24d2^: «-8589934592␤» ¦ec18f24,2015.12,HEAD(5929887): «3.6014305115␤» (2015-12-17) https://github.com/rakudo/rakudo/commit/ec18f24d27ce61fa71d177ab76c4044ee1d1a75e The second

[perl #124161] [BUG] failure to bind to pointy block param

Still reproducible (2017.11, HEAD(5929887)). Not sure if that's NYI or LTA. I'll mark as both. On 2015-03-23 15:12:59, jdv79 wrote: > Hello, > > Please see below. > > -jdv > > 18:04 < jdv79> m: my @a = 1; for @a -> $a is rw { $a := 2; } # that > error isn't clear as to why; at > least to me >

[perl #123060] [BUG] `$++` statements in routines sometimes give the anonymous variable `my` scoping, sometimes `state` scoping in Rakudo

Still reproducible (2017.11, HEAD(5929887)) On 2014-10-26 08:58:08, masak wrote: > as for $ = 'A', currently that's equivalent to (state $) = > 'A', since the $ doesn't actually parse as a declarator, but is > promoted to a declaration in the actions > maybe we can fix that somehow > could

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

Still reproducible (2017.11, HEAD(5929887)), but is supposed to work? On 2015-02-09 17:43:52, rayd...@cyberuniverses.com wrote: > m: my $a; BEGIN { $a := 1; say $a; }; say $a; > rakudo-{parrot,moar} 0cb22e: OUTPUT«1␤(Any)␤» > > m: my $a; BEGIN { $a = 1; say $a; }; say $a; # works with assignment

[perl #123583] [BUG] Two different enum values with the same short name should "poison" the slot they're in, rather than refuse to merge global symbols in Rakudo

Still reproducible (2017.11, HEAD(5929887)), but with a slightly different error: ===SORRY!=== Error while compiling -e Cannot import the following symbols from X, because they already exist in this lexical scope: B, A at -e:1 --> use X⏏; use Y On 2015-01-11 05:44:26, masak wrote: > here:

[perl #124018] Differing behavior of multi grammar rules with and without "multi"

Still reproducible (2017.11, HEAD(5929887)). It does print Nil instead of (Any), but same thing. On 2015-03-08 09:22:25, b...@abrij.org wrote: > > In a grammar that uses a proto+parameterized multi, the "multi" is > optional according to S05. However, the presence of the "multi" > seems to prevent

[perl #121843] my @words <== sort <== ("c", "b", "a"); # feed failing to parse

Still reproducible (2017.11, HEAD(5929887)) On 2014-05-10 14:42:47, david.warring wrote: > Golfed from fudged test in integration/advent2010-day10.t > > $ perl6-m -e'my @o <== sort <== ("c", "b", "a")' > Unable to parse expression in quote words; couldn't find final '>' > > at -e:1 > --> my

[perl #119401] [BUG] < $< $> > yields a one-element list, not a two-element list in Rakudo

OP Still reproducible (2017.11, HEAD(5929887)) On 2013-08-21 05:40:22, masak wrote: > r: .say for < $< $> > # rakudobug ? > rakudo e84dda: OUTPUT«$<$>␤» > Yeah. I would have expected "$<\n$>\n" > r: < $< $> >.perl.say > rakudo e84dda: OUTPUT«("\$<\$>",).list␤» > Yeah. Odd > * masak submits

[perl #123216] [BUG] QRPA: Can't pop from an empty array!

Heh, what a clusterfuck! OK let's try to untangle this ticket. The second issue mentioned in this ticket (MVMArray: Can't pop from an empty array) was fixed. ✓ Output on all releases: https://gist.github.com/Whateverable/5d30c8b09af4ddee8bdb67693cd0f6e0 Fixed in (2015-03-30)

[perl #121987] Negated generic comparisons do not chain correctly

Still failing (2017.11, HEAD(5929887)) On 2014-07-31 13:05:19, david.warring wrote: > I've added some fudged tests to S03-operators/relational.t. A couple > taken from the above test cases, also: > > is 3 !> 3 !> 1, 3 !> 3 && 3 !> 1, 'chained !>'; > is 3 !< 3 !< 2, 3 !< 3 && 3 !< 2, 'chained !<';

[perl #123596] vars from subsigs are not available to where blocks

Interesting. Still reproducible (2017.11, HEAD(5929887)) On 2015-01-14 03:05:38, FROGGS.de wrote: > FROGGS: m: multi car($x, [$y, @ys] where $x == 1) {1}; say car 1, [1, > [2, 3]]; > camelia: rakudo-moar d69491: OUTPUT«1␤» > FROGGS: m: multi car($x, [$y, @ys] where $x == $y) {1}; say car 1, [1, >

[perl #123862] [BUG] Negative exponents not parsed in radix literals

Still reproducible (2017.11, HEAD(5929887)) On 2015-03-10 14:55:48, david.warring wrote: > On Tue Feb 17 11:20:39 2015, Mouq wrote: > > GitHub user MARTIMM submitted the following bug to the > > Roast GitHub issues ( https://github.com/perl6/roast/issues/53 ) > > > > Reading

[perl #123979] %064b format doesn't deal with negatives

It is actually fixed now: ¦2015.12,b2fbf893db^: «-1100100» ¦b2fbf89,HEAD(5929887): «-1100100» That comes from this bump: (2017-11-13)

[perl #124098] [PERF] Passing an argument list to the export trait slows the parse stage down a lot.

I can reproduce. The difference at 2017.11-36-g78caeb6bc is ≈0.133s vs ≈0.732s On 2015-03-17 05:58:27, pe...@reproducible.io wrote: > First reduced test-case (no argument): > > constant C1 is export = 1; > constant C2 is export = 2; > constant C3 is export = 3; > constant C4 is export = 4; >

[perl #124434] [BUG] Passing an Exception object to Failure.new segfaults (SEGV) in sink context in Rakudo

Heh, this behavior lives its own life. See https://gist.github.com/Whateverable/df882a7545b2aa4cd0575909934f4c48 Since 2017.07 it is producing this message: Died with Exception Actually thrown at: in block at /tmp/m_9jvp4WTp line 1 I think that's reasonable. Marking as ｢testneeded｣. On

[perl #126102] [BUG] Rat.perl doesn't round-trip numerical value

OK, there are two problems mentioned in the report. The second one (with 0.A being created) is part of RT#126016 which is now resolved. ✓ As for the other issue, the behavior has changed a little bit: my $a = 0.8999; my $b = $a.perl.EVAL; say $a.WHICH; say $b.WHICH

[perl #123457] enum A "P6opaque: no such attribute '$!signature'"

This was fixed in (2015-12-13) https://github.com/rakudo/rakudo/commit/3c81e335f3a327e4cacee993d1b5f265dfe3706e W4anD0eR96++ added tests in https://github.com/perl6/roast/commit/89a96af777 Closing. On 2015-01-08 12:47:58, jn...@jnthn.net wrote: > On Thu Dec 18 19:01:29 2014, raiph wrote: > >

[perl #125488] Some phaser blorsts don't see outer $_

This was resolved in (2016-08-03) https://github.com/rakudo/rakudo/commit/5e61516a3fd290d93a7e18899483ccb2b9ba3a30 W4anD0eR96 committed some tests for it: https://github.com/perl6/roast/commit/48124e0123c27a7c5f140eb0602a15a32a56 And then beefed up the tests for other phasers:

[perl #116719] [BUG] Internal error message on Z=> in enum declaration in Rakudo

Yeah, this is not correct, and it was resolved in (2017-11-27) https://github.com/rakudo/rakudo/commit/d9021cf16e7df051c5e17c33919c9bde44c5e0db Now you may wonder when the original “Method 'returns' not found” was fixed, and… that was on Parrot :) So not really bisectable and not even relevant

[perl #132525] [BUG] type constraints to Array[Pair] don't work when precompiled

# New Ticket Created by Dan Zwell # Please include the string: [perl #132525] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132525 > The following function runs fine when it's not defined in an external file: our sub