[perl #123452] [BUG] Grammar fails unexpectedly and then succeeds when Grammar::Tracer is imported in Rakudo

TimToady_: ooc, do you agree that tracing a grammar breaks LTM matching? https://github.com/jnthn/grammar-debugger/issues/13#issuecomment-229940842 The solution, for whoever fancies implementing it, is probably to mix a role into the tracing closure that we hand back. Where said role has the

[perl #126827] [BUG] Class declaration from one module not visible if another module is loaded after it with a very similar class declaration in Rakudo

masak: I still doubt it's actually 8728828 that's to blame. Between 3b943782 and 8728828 there's a lot of refactoring, especially some changes touching the handling of global merging. Might be a good idea to bisect that (with manual precompilation in every step) nine: will do. [...] nine: t

[perl #126827] [BUG] Class declaration from one module not visible if another module is loaded after it with a very similar class declaration in Rakudo

masak: if 87288285f6f398ec7cba0900312ced4b580d79ed is to blame, it may just be an older precompilation issue that surfaced because we precompile everything that's too slow to run away now... masak: to find that out, it would help if you could test with a version before 3b943782768260d4422933f4

[perl #125595] [LHF] LTA error message with malformed loops

alex (>): > Code: > loop (my $i = 0; $i <= 5; $i++;) { say } > > Result: > ===SORRY!=== Error while compiling ./test.pl > Missing block > at ./test.pl:2 > --> loop (my $i = 0; $i <= 5; $i++⏏;) { say } Interesting failure mode. That semicolon looks unnecessary but harmless to me. (It's of the

[perl #109322] [BUG] Lexical weirdness from blocks inside re-entrant subs in Rakudo

A bit late to the game, but... here's a shorter version: m: my $y = 1; sub foo($x) { $y-- && foo("z"); { say $x } }; foo("x") rakudo-moar d179b4: OUTPUT«z␤z␤» again, should say "z␤x␤" * masak adds the example to RT #109322

[perl #125289] [BUG] Array with pair written with the value implicitly True, [:a], won't evaluate (or .perl) properly in Rakudo

Fixed (37e2c9), spectested (c2effba). Resolving ticket.

[perl #125242] .perl method fails on hashes with type-constrained keys

lizmat (>) > This appears fixed with 869306336fadd85320bfc1 Resolving ticket.

[perl #62086] ~ in regexes shouldn't cause thrown exceptions

On Mon May 11 05:26:45 2015, pmichaud wrote: > After discussion with jnthn at OSDC.no, here's what we propose: > > In the regex engine, the default FAILGOAL behavior should be to simply > fail/backtrack. This would be the default behavior for (rakudo) > Cursor as well. > > Grammars that wish to

[perl #125101] Newline before => breaking parse

labster (>): > It sounds like this is intentional behavior. Indeed. Rejecting ticket.

[perl #116370] [BUG] a macro with $_ as an argument doesn't work in a statement_mod 'for' loop in Rakudo

bartolin (>): > But back in 2013 the output was «4␤5␤6␤». I'd say «4␤5␤6␤» is the correct output. There's nothing to suggest to me that it should get stuck on 4. So either this ticket should be closed (because the original problem is now gone) and another one opened with the new problem, or thi

[perl #124317] Possible type signature bug

Fixed and tested as of 1c916bc. Resolving ticket.

[perl #124317] Possible type signature bug

I should probably start by looking at the RT queue notably #124321 Calling .^make_pun is surely wrong It'll create one every time .^inheritalize gets the pun Though maybe we should have a .^pun that does similar, and make inheritalize delegate to it. ok, so that was easy. the problem is in.

[perl #117853] [BUG] can't assign here documents to constants

masak: I think https://rt.perl.org/Ticket/Display.html?id=117853 can get a test (if there isnt' already one) and be closed now? jnthn: yep. was gonna add that to the ticket. * masak adds it now

[perl #124191] [BUG] For loop fails to CATCH exception on 208th iteration in Rakudo

so, I just removed https://github.com/rakudo/rakudo/blob/nom/src/vm/moar/Perl6/Ops.nqp#L460 locally; RT #124191 is still present afterwards :/ Link: https://rt.perl.org/rt3//Public/Bug/Display.html?id=124191 so it's something deeper, then. rakudo/nom: ee7a375 | jnthn++ | src/vm/moar/Perl6/Ops

[perl #124191] [BUG] For loop fails to CATCH exception on 208th iteration in Rakudo

masak (>): > Tux says something recent caused the above failure. I'd really > appreciate it if someone wanted bisect (maybe a month back or so). I did a bisect, which revealed a number of things. All of the findings below can be reproduced by the following commands: $ git clone g...@github.

[perl #124190] [BUG] Promise::Vow can be constructed from the outside to change the status of a Promise in Rakudo

Fixed in fb991b and spectested in 4f7877. Resolving ticket.

[perl #102652] [BUG] Rakudo recommends a different syntax for do...for loops and then that syntax doesn't work

bri (>): > So this might be a closeable ticket now? Yes, I would say so. Good work. Resolving.

[perl #116212] [BUG] 'Hash of Hash' line causes REPL to segfault in Rakudo

On Sat Jan 24 13:52:59 2015, barto...@gmx.de wrote: > As a status update: I don't get a segfault in the REPL with a current > rakudo (tested on moar, parrot and jvm). > > The error message has changed slightly: More exactly, the segfault is now gone. m: class Foo { has Hash of Hash $.foo = {} }

[perl #62086] ~ in regexes shouldn't cause thrown exceptions

as an author of grammars, I still find it annoying and difficult that grammars generally fail, that is, return a failing match -- *unless* you use the `~` combinator, in which case they nqp::die with an exception that can't be properly caught using a CATCH. in effect, that gives grammars three

[perl #123581] Infinite lists match [] signature

m: (1..*).Capture.perl.say rakudo-moar 6a3fc3: OUTPUT«Capture.new(hash => {"excludes-max" => Bool::False, "excludes-min" => Bool::False, "min" => 1, "max" => Inf})␤» ah m: (my @a = 1..*).Capture.perl.say rakudo-moar 6a3fc3: OUTPUT«Capture.new()␤» That's a golf. * masak adds that to the ticke

[perl #123452] [BUG] Grammar fails unexpectedly and then succeeds when Grammar::Tracer is imported in Rakudo

I need to digest those comments, though. I don't understand where the grammar "eats the newline that TOP needs to progress". and, oh yes, I also noticed that changing 'token x' to 'regex x' made the bug go away. that's one thing I failed to include. ...but anyway. even not following all the de

[perl #123452] [BUG] Grammar fails unexpectedly and then succeeds when Grammar::Tracer is imported in Rakudo

masak: no, it makes the grammar behave wrong, it turns out in parsing B\n, it matches the right side of x under LTM, and eats the newline that TOP needs to progress, so the next match fails to progress because $$ doesn't match put a {} before the second \s* and it matches, because then it ties

[perl #123116] [BUG] Weird error for code parameters with subsignatures in Rakudo

masak (>): > I am not 100% sure the `&block (Dog --> Bool)` form should work, > or is by spec. The `&block:(Dog --> Bool)` form comes from S06:1675. at one point we required a : because of the ambiguity with sublists of parameters, but we already have a whitespace dep with @foo[3,3] vs @foo [$x

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

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 also argue that it should be restricted to integers * TimToady loves to argue so much that he

[perl #99658] sequence operator '...' timeout

bartolin (>): > Actually I don't think S03 says that '1,3,5 ... 8' should act as > '1,3,5 ... *' > > As I understand it '1,3,5 ... 8' gives an infinite list with all even > numbers. '1,3,5 ... *' also gives an infinite list with all even > numbers -- but this one is lazy. > > So there is a differ

[perl #118581] [BUG] Segfault for a signature match with a native type and an 'as' cast in Rakudo

Resolving this ticket because Rakudo no longer segfaults. See [perl #122990] for the unexpected behavior it revealed underneath.

[perl #118067] [BUG] Null PMC access when calling .new on a subclass with a proto overriding the regular .new in Rakudo

On Thu Oct 16 00:10:27 2014, barto...@gmx.de wrote: > Just an update: There is no longer a Null PMC access error, but Rakudo > complains about no matching signature: > > $ perl6-m -e 'class A is Any { proto method new($) {*} }; A.new(now)' > Cannot call 'new'; none of these signatures match: > i

[perl #122983] [BUG] spurt busted in Rakudo

Ah, yes. Rebuilding enough things, it works now. FROGGS (>): > I almost want to tag the bug as invalid :o) Done.

[perl #122983] [BUG] spurt busted in Rakudo

I found the error message that spurt emits. it's in Moar. https://github.com/MoarVM/MoarVM/blob/256554b8a23cb226e374b4dd57e8af668d2654c1/src/io/syncfile.c#L89 FROGGS++ has since made that error not happen: https://github.com/MoarVM/MoarVM/commit/03ac9a70f6dee026a

[perl #117773] [BUG] KeyBag accepts non-UInt values in Rakudo

bartolin (>): > That looks reasonable to me. Is the ticket closable with tests? Yes, I think so.

[perl #113988] [BUG] Null PMC access when doing .fmt on the return value from .reals

Christian (>): > So maybe instead of closing this ticket we should change the subject > of this ticket to 'LTA error message when .sprintf is called with more > directives than arguments (numeric)'? No need to keep it open for that, methinks. There's already https://rt.perl.org/Ticket/Display.htm

[perl #116016] [BUG] The rule to match routines/symbols is overriding the rule to match versions, because of LTM

std: say v2013.4.5 std fc92e1e: OUTPUT«===SORRY!===␤Confused at /tmp/W0MHCqFo4M line 1:␤--> say v2013.⏏4.5 [...] aha :-) looks like STD and Rakudo agree here about multi-digit version numbers I recognize this failure mode. we've encountered it before it's a longest-token-matching iss

[perl #122904] a wrong regex in UsingPerl6-draft.pdf

On Sat Oct 04 06:09:57 2014, songwen...@linuxdeepin.com wrote: > Page 99 > > If you quantify a capture, the corresponding entry in the match object > is a list of other > match objects: > > > > > right regex is m/(\w+)+ % [\,\s*] \s* 'and' \s* (\w+)/ Fixed, thanks! https://github.com/perl6/b

[perl #122882] [BUG] Symmetric set difference (^) doesn't right-associate or chain in Rakudo

$ 6 'say (^) (^) ' set(b) #122882 can be marked as TEST NEEDED :-) Marked as testneeded.

[perl #122746] [BUG] Stringification of AST parameter not captured properly in postfix macro in Rakudo

masak (>): > m: macro postfix:($o) { quasi { die "Null check failed for > ", $o.Str unless defined {{{$o}}}; {{{$o}}} } }; say 42!!; my > $cookies; my $food = $cookies!! > 16:18 <+camelia> rakudo-moar 51ddd5: OUTPUT«42␤Null check failed for ␤ > in any [...]» > so close. > * masak submits rakudob

[perl #85750] Test failures on OpenBSD

masak: S03-operators/arith.t mentions http://mathworld.wolfram.com/Indeterminate.html, as I understand it this argues in favour of 1 ** Inf == NaN bartolin: sure, I'm already concinced that *math* makes the argument for 1 ** Inf == NaN. but IEEE 754 deviates from math in some places where it

[perl #85750] Test failures on OpenBSD

p6: say 1 ** Inf # [RT #85750] niecza: OUTPUT«Cannot open assembly './run/Niecza.exe': No such file or directory.␤» ..rakudo-jvm d60a8f: OUTPUT«Can't call method "syswrite" on an undefined value at /home/p6eval/jvm-rakudo/eval-client.pl line 32.␤» ..rakudo-{parrot,moar} d60a8f: OUTPUT«1␤» th

[perl #122882] [BUG] Symmetric set difference (^) doesn't right-associate or chain in Rakudo

see my response to RT #122882 :) mainly, infix:<(^)> should list associate imo, (^) (^)should result in more to the point, (^) (^) should result inand not , which is hard to do if (^) is left-assoc pmichaud: I agree. that rhymes with infix:<^^> semantics, too. exactly.

[perl #122679] White space breaks feed syntax ==> with grep and map - bogus statement

Kevin (>): > I was playing with Game::Crypt \o/ > and ran into the following problem. > Compile crashes with a Bogus statement error. It seems that the > insertion of a newline breaks the compile. I don't think this is perlsh > behaviour! > > The following code reproduces it: > > use v6; >

[perl #77334] [BUG] For loops fail to decontainerize in Rakudo

n: sub foo { my $s = 0; ($s += $_ for 1..3) }; say foo() niecza v24-109-g48a8de3: OUTPUT«1 3 6␤» this is a data point, too. Niecza decontainerizes.

[perl #77334] [BUG] For loops don't decontainerize in Rakudo, and maybe they should

<[Coke]> rant: old tickets with "maybe" or "either std or rakudo is wrong" [Coke]: if I'm to blame for "either std or rakudo is wrong" tickets, send them to me and I'll take action on them. I'm pretty sure I don't file "maybe" tickets :) <[Coke]> masak: RT #77334 Link: https://rt.perl.org/rt3//

[perl #122654] [BUG] Operator starting with a bang (!) and having a Unicode character in it not recognized by Rakudo

Heh; just in case someone takes a close look at that error message and is terribly confused... here's the correctly pasted one: m: multi infix:«≃» { $^l lt $^r }; multi infix:«!≃» { not($^l ≃ $^r) }; say "foo" !≃ "bar" rakudo-moar d8c834: OUTPUT«===SORRY!=== Error while compiling /tmp/weCLGmo

[perl #83622] [BUG] Rakudo says NaN === NaN is False

masak (>>>), coke (>): > > > rakudo: say NaN === NaN > > > rakudo a37640: OUTPUT«Bool::False␤» > > > that one could be true, since it's asking a non-numeric > > > question > > [...] > > Fixed in a82c407. I just want to add, for completion, that discussion on #perl6 mentioned that there are dif

[perl #65172] .ord() does not work on graphemes

Is \w defined as on purpose? yes It is not in perl5 no? With the very good reason that it matches combining chars for example m: say 'xyz̧p' ~~ /\w+/ rakudo-moar 4cad54: OUTPUT«｢xyz｣␤␤» those are meant to be deal with at grapheme level in p6 Right; that's a lack of NFG... oh, so the abov

[perl #122011] FIRST and LAST behave inconsistently (and annoyingly)

Commit 1bb76a6 in roast adds a test (in S04-phasers/in-loop.t) for the expectation expressed in this ticket: that LAST not fire if the loop doesn't have iterations.

[perl #121909] [LHF] Numeric shift +> misbehaving on parrot - Dates broken

p: my $d = Date.new(:year(2012), :day(1), :month(12)); say ++$d rakudo-parrot 166bf3: OUTPUT«2012-12-02␤» seems https://rt.perl.org/Public/Bug/Display.html?id=121909 is fixed? masak: https://rt.perl.org/Public/Bug/Display.html?id=121909 doesn't error for me * masak resolves ticket

[perl #121249] [BUG] Configure.pl not giving enough hints about what options to use when building with MoarVM as the backend

nqp: 1658541 | jnthn++ | Configure.pl: nqp: Give a hint about --gen-moar when no moar is found nqp: review: https://github.com/perl6/nqp/commit/16585410c9 masak: Hopefully 1658541 helps a little jnthn++ ok, resolving the rakudobug.

[perl #121147] The last bug

<[Coke]> masak: if none of them have RT #121147 right, what's the right way to have it? [Coke]: sorry, left that out. [Coke]: "Here\n" [Coke]: with the rationale that FIRST runs before any iteration, the say gets printed, and then 'last' quits the loop. [Coke]: rakudo-moar seems to entirely

[perl #119999] [BUG] LTA internal Parrot error when doing '&::{}' in Rakudo

current instr.: 'variable_components' pc 26971 (src/gen/perl6- symboltable.pir:10438) (src/Perl6/World.nqp:1858) if you run it with --ll-exception * masak adds that to the ticket moritz++

[perl #119919] LTA Error Message for operator declaration with []

lue (>): > The infix:["..."] form of declaration should at least have a better > error message. Not just that. S02, S03, S06, and S12 contain examples of this syntax. So at the upper end this should actually be allowed, not just have a better error message. Of course, arbitrary values inside t

[perl #98954] [BUG] Nested indexing semantics changed from Beijing to nom in Rakudo

On Mon Sep 12 15:04:09 2011, masak wrote: > b: my @a = [1], [2], [3]; say (map { @a[1 - $_][0] }, 0 .. > 3).perl > b 1b7dd1: OUTPUT«(2, 1, Any, Any)␤» > nom: my @a = [1], [2], [3]; say (map { @a[1 - $_][0] }, 0 .. > 3).perl > nom 08ef94: OUTPUT«(2, 1).list␤» > * masak submits rakudobug > here

[perl #111734] [BUG] Can't locally redefine True in Rakudo

masak (>): > Nope, not fixed: > > r: constant True = "Yeah, well, you know, that's just, like, > your opinion, man."; say True > rakudo b2072f: OUTPUT«True␤» > * masak adds to https://rt.perl.org/rt3/Public/Bug/Display.html? > id=111734 This now appears to be fixed: r: constant True = "yeah,

[perl #114014] ord.Cool outputs LTA error

< masak> moritz: what error message would I have expected? the one STD gave at the end of the original message. < masak> "Unsupported use of bare 'ord'; in Perl 6 please use .ord if you meant $_, or use an explicit invocant or argument" * masak adds that to the ticket

[perl #109874] BUG: should match: grammar A { rule TOP { ^ } }; say A.parse(' ')

r: grammar G { token TOP { ^$ }; rule foo { foo } }; say ? G.parse(" foo") rakudo 96776b: OUTPUT«True␤» r: grammar G { token TOP { ^$ }; rule foo {foo } }; say ? G.parse(" foo") rakudo 96776b: OUTPUT«False␤» I thought rules ignored initial whitespace... masak: it's fascinating how rakudo stil

[perl #118737] [BUG] Match object loses its inner match if <$rx> regex inclusion syntax is used in Rakudo

the problem with /(<$re>)/ is that the <> is still going to throw away the captured material inside because it doesn't start with alpha oh! r: my $re = rx {.(.).}; say 'abc' ~~ /$0=<$re>/ rakudo ce8b5f: OUTPUT«｢abc｣␤ 0 => ｢abc｣␤ 0 => ｢b｣␤␤» \o/ TimToady: so the rakudobug is a dud? /(<$re>

[perl #118601] [BUG] sprintf %d loses digits in Rakudo

rn: say sprintf "%d %d", 301281685344656640, 301281685344656669 niecza v24-81-g6672fa2: OUTPUT«301281685344656640 301281685344656669␤» ..rakudo d02067: OUTPUT«-1202938624 -1202938595␤» masak: I think that your bug title for RT #118601 is incorrect, but we seem to have two related bugs here n

[perl #111734] [BUG] Can't locally redefine True in Rakudo

On Sun Jun 09 08:00:22 2013, jn...@jnthn.net wrote: > On Tue Mar 13 13:35:18 2012, masak wrote: > > nom: constant True = 42; say True > > rakudo fee891: OUTPUT«True␤» > > hm. > > r: constant True = 42; say +True > > rakudo fee891: OUTPUT«1␤» > > Huh > > * masak submits rakudobug > > good rak

[perl #64928] The undefinedness of optional arguments and typed attributes in Rakudo

On Tue Apr 21 06:35:05 2009, masak wrote: > but... I just want a nice way to see if the hash was passed or > not. > [...] > the problem is that we're doing in-band communication > instead of asking the hash parameter if it was defined, we > should ask the capture if that hash was given > aye. >

[perl #118227] [BUG] hyper-adding does not respect hash typedness in Rakudo

Liz (>): > Feels like this in essence is the same as .clone not being able to > clone a typed hash. Yes, at least for some of the simpler cases. After I submitted the ticket, this relevant discussion took place: pmichaud: hm. question is, if I %h1 >>+<< $h2, and the hashes are typed with diffe

[perl #114760] [BUG] Minus thirteen billion years ago becomes minus 115 million years ago in DateTime.new in Rakudo

masak (>>), coke (>): > > r: say Date.new(-13_000_000_000, 1, 1) > > rakudo cc1858: OUTPUT«-115098112-01-01␤» > > o.O > > I suppose -115098112 above is a bug? > > r: say -13_000_000_000 > > rakudo cc1858: OUTPUT«-130␤» > > * masak submits rakudobug > > This seems consistent with tryi

[perl #118179] FIRST doesn't see lexicals from surrounding block

coke (>): > I expected it to mean "the FIRST time a block is executed". > > My workaround was to use a lexical to track if it was the first time > through the loop or not; > will stick with that. [Coke]: doesn't START do exactly what you wanted from FIRST? r: for 1..10 { my $a = 3; START { say

[perl #112276] [TODO] Implement 0-arg slurp in Rakudo

On Tue May 21 00:22:55 2013, labster wrote: > On Tue Nov 20 18:56:50 2012, coke wrote: > > On Thu Apr 05 05:44:37 2012, masak wrote: > > > p6: say $*IN.slurp.comb(/e/).elems > > > rakudo 4373f0, niecza v15-6-gefda208: OUTPUT«88␤» > > > r: say slurp.comb(/e/).elems > > > > Both of these now say

[perl #101440] [BUG] Closures created inside BEGIN blocks see the wrong outer lexpad in Rakudo

masak (>>), coke (>): > > nom: my $c; my $name; BEGIN { $c = { say "OH HAI $name" } }; > > $name = "masak"; $c() > > nom ea25f3: OUTPUT«Use of uninitialized value in string > > context␤OH HAI ␤» > > I'd expect the above to say "OH HAI masak". > > are my expectations too high? :) > > masak: See

[perl #117935] [BUG] Sending named parameter ;p with value 0 to .postfix:<{ }> should yield the value and not the pair in Rakudo

actually, the :p(0) also applies to :delete and :exists rn: my %a; %a=1; say %a:delete(0); say %a rakudo 2a04f2: OUTPUT«1␤().hash␤» ..niecza v24-50-gba63d9a: OUTPUT«1␤{}␤» lizmat: Correct. * masak adds that to the ticket

[perl #78316] [BUG] Weird error when doing .perl on .^attributes in Rakudo

On Wed Feb 01 06:28:26 2012, coke wrote: > On Sun Oct 10 16:05:36 2010, masak wrote: > > rakudo: class Car { has @.wheels }; say Car.^attributes > > rakudo 5bdbd4: OUTPUT«@!wheels␤» > > rakudo: class Car { has @.wheels }; say Car.^attributes.perl > > rakudo 5bdbd4: OUTPUT«Method 'attributes' no

[perl #111518] [BUG] Regex engine doesn't publish match variables early enough in some cases in Rakudo

rn: say 1001110011 ~~ /^ (.+) $0+ @([\~] $0.comb)? $ / niecza v24-48-g1d127e4: OUTPUT«｢1001110011｣␤ 0 => ｢10011｣␤␤» ..rakudo bfd850: OUTPUT«No such method 'comb' for invocant of type 'Any'␤ in regex at /tmp/OHj0MG5jaw:1␤ in method ACCEPTS at src/gen/CORE.setting:10370␤ in method ACCEPTS at

[perl #117951] [BUG] $%*ENV doesn't work in Rakudo, dies with a deprecation warning about $%

masak: please link that patch too: https://github.com/sorear/niecza/commit/1d127e411e FROGGS: oh, will do. thanks

[perl #117933] [BUG] Something is going wrong with infix: on a 64-bit boundary with big integers in Rakudo

rn: say 2804985923338703271682399481743033703427656749129565173066 mod 256 rakudo fe7049: OUTPUT«36902553666127019859637446314758035961162␤» ..niecza v24-42-g69a3432: OUTPUT«74␤» and there's your bug colomon++ rn: say 2804985923338703271682399481743033703427656749129565173066 % 256 rakudo

[perl #113988] [BUG] Null PMC access when doing .fmt on the return value from .reals

coke: > Lists's .fmt is using the full format on each value in the list, so > you get the same effect with: > > > 3.fmt("%d %d"); > Null PMC access in get_integer() So it's a dupe of , really. I could merge them; any objections?

[perl #117307] [BUG] Sequences with strings and a Code stopping condition go backwards in Rakudo

Pm (>): > S03 has: > > For functions deduced when there is only one value on the left, > the final value is used to determine whether *.succ or *.pred is > more appropriate. The two values are compared with C to > determine the direction of the progression. > > Rakudo evaluate

[perl #117217] [BUG] '...' and '???' forms of stub code escape 'try' statement in Rakudo

??? should warn. ... should fail The fail leaks out of the try er, or either way the fail is in sink context a fail in sink context throws. ??? is correct in Rakudo ... is debatable there; I think the current spec says that try sinks everything inside of it, in which case it shoulda sunk, f

[perl #117171] [BUG] [WEIRD] Internal Parrot error when doing this thing in Rakudo

it's not an internal parrot error; it's the stringification of the pseudo-stash * masak adds this to the ticket r: say ::.Str rakudo 1c9939: OUTPUT«GLOBALish 7 EXPORT11 $?PACKAGE 15 ::?PACKAGE 19 $_ 23 $/ 27 $! 39 $=pod43 !UNIT_MARKER 51␤» if it's just a stash, sho

[perl #117113] [BUG] Bogus error about 'outside of any Routine' when returning from inside of a for loop in a routine in Rakudo

r: sub x { sink return 5 for 1 }; say x rakudo 8ea992: OUTPUT«5␤» looks like sink context to me I believe it's caused by the fact that rakudo doesn't do lexotic binding of the return to the sub that's bitten me with gather/take as well * masak adds this to the ticket

[perl #117113] [BUG] Bogus error about 'outside of any Routine' when returning in sink context from inside of a for loop in a routine in Rakudo

r: sub x { return 5 for 1 }; say x rakudo 8ea992: OUTPUT«Attempt to return outside of any Routine [...] no, it's not sink context. * masak adds to the ticket should I unassign moritz? :) better not. something tells me that even if this isn't directly related to sink context, maybe it's indir

[perl #117109] [BUG] .pick doesn't flatten in Rakudo

rn: say (<0 1> xx 5).roll rakudo 8ea992, niecza v24-33-gfc6d5fd: OUTPUT«0 1␤» hm. Well, I'll do the usual thing with flattening related tickets: wait for pmichaud++ to comment on the ticket ;) I suspect this one should do what you expect though. but Rakudo and Niecza agree on .roll -- that m

[perl #116695] [BUG] Wrong array length when Mu elements and delete interact in Rakudo

don't know about nqp, but on JVM we keep a constant value in QRPA which says how many elements are there it probably needs to be updated when we set Mu somewhere the problem is that if you delete an element that's not the last, it set to Mu because we don't have an offchannel way to store an

[perl #116595] [BUG] Nesting wrapping roles bind 'callsame' to the wrong recipient in Rakudo

rn: role F[$n] { method x { callsame; callsame until $.v % $n } }; class S { has $.v is rw = 1; method x { ++$.v } }; my $s = S.new; for ^3 { $s.x; say $s.v; $s = $s but F[$s.v] } niecza v24-18-gaf64300: OUTPUT«2␤3␤5␤» ..rakudo b3fc32: OUTPUT«(timeout)2␤3␤» jnthn: this is as short as I'm able

[perl #116521] [BUG] 'state' is seriously broken in Rakudo

On Wed Jan 23 02:35:53 2013, masak wrote: > I'm not one to use "it's broken" as a bug ticket description -- I > think it's bad style. But this is the exception that proves the rule: > somehow state not only isn't doing what it says on the tin, but it > breaks parsing, too. > > nr: sub f { say ++s

[perl #70297] [BUG] No explicit ^D and no newline after ^D in the REPL in Rakudo

On Sat Oct 01 15:16:23 2011, masak wrote: > On Sat Oct 01 04:22:04 2011, moritz wrote: > > Now a EOF (Ctrl+D) is answered with a newline, and the REPL exits. > > > > Closing without spectests, because the REPL isn't specced. > > As the original submitter, I'm reopening the ticket because only one

[perl #116280] [BUG] NaN, Inf, -Inf aren't padded with spaces in sprintf in Rakudo

On Tue Jan 08 11:40:37 2013, FROGGS.de wrote: > This would mean to bring over 500 lines of C code to nqp/rakudo. Is that an absolute claim? What about wrappers? > And this would mean that it doesn't get faster. Is it worth it? In my mind, correctness trumps speed. The current behavior seems obv

[perl #116314] [BUG] 'for' loops in phasers in 'for' loops don't run in Rakudo

masak: fwiw https://rt.perl.org/rt3/Ticket/Display.html? id=116314 is about the phasers not being put in sink context properly moritz: show me your reasons for believing this. masak: for loops are lazy, and only run in eager or sink context masak: so if normal statements are run, but for loops

[perl #116220] [BUG] Can't talk about roles with unimplemented methods in Rakudo

also: its not just stringification methods, it seems that calling any method at all on a role with required methods is broken r: role Foo { method bar {...} }; say Foo.^name rakudo c8de2e: OUTPUT«Method 'bar' must be implemented by Foo because it is required by a role [...] :/ r: role Foo {

[perl #79116] [BUG] Non-associative operators mistakingly allowed in reduction meta-op

On Fri Nov 12 07:37:03 2010, Solomon wrote: > rakudo: say [leg] > p6eval: rakudo d85964: OUTPUT«-1␤» > > ...but... > > "Any infix operator (except for non-associating operators) can be > surrounded by square brackets in term position to create a list > operator that reduces using that operation.

[perl #113904] [BUG] Null PMC Access when blocks get the wrong $_ sometimes in Rakudo

r: my $line; for < one two three >.values -> $line { if True { .say } } rakudo bf472b: OUTPUT«Null PMC access [...] huh. we may have this in RT already, actually. r: for 1 -> $ { if 1 { .say } } rakudo bf472b: OUTPUT«Null PMC access [...] yes, here: https://rt.perl.org/rt3/Ticket/Display.ht

[perl #115740] bare '=pod' does not count as "abbreviated block"

On Thu Nov 15 05:14:34 2012, pawel.pab...@implix.com wrote: > Rakudo 2012.10 > > bbkr_ r: =pod > p6evalrakudo c82d10: OUTPUT«===SORRY!===␤Preceding context expects a > term, but found infix = instead␤at /tmp/eqe30h6iti:1␤» > bbkr_ std: =pod > p6evalstd 04216b1: OUTPUT«ok 00:00 40m

[perl #72696] [BUG] Defining two different enumerations with the same enum value should result in ambiguity in Rakudo; doesn't

On Thu Nov 15 05:16:59 2012, bbkr wrote: > 2012.10 - still broken (should fail on redeclaration) > > rakudo: enum A ; enum B ; say c.perl > rakudo c82d10: OUTPUT«B::c␤» Just for the record; no, it shouldn't fail on redeclaration (despite STD's error message). The spec says that the a, b, and

[perl #115506] [BUG] Bad failure mode when macro returns AST.new in Rakudo

coke (>): > I was unable to test this: > > #RT #115506 > eval_lives_ok > "macro pathological { AST.new }; pathological();", > "macro returning AST.new doesn't blow up"; > > fails with: > > prove -v -e t/fudgeandrun t/spec/S06-macros/errors.tt/spec/S06- > macros/errors.t .. > 1..1 > not o

[perl #115712] [BUG] When somebody sets up it the BOM, all our base are not belong to Rakudo

On Tue Nov 13 04:29:08 2012, masak wrote: > I wonder why we shouldn't simply strip the BOM in Rakudo if we > find it. The grammar now ignores BOM at the start of a compilation unit. Spectest added. Resolving ticket.

[perl #115608] [BUG] Cannot call a routine using 'foo' syntax when a module 'foo' is declared in Rakudo

module foo; sub foo() { say "OH HAI" }; foo; foo() In this one, foo() parses as a coercion. jnthn: oh! * masak adds that to the appropriate rakudobug Anyway, it's right it doesn't call the sub. Just an LTA error I guess...though I ain't immediately sure what to do with it...

[perl #115506] [BUG] Bad failure mode when macro returns AST.new in Rakudo

On Sat Oct 27 10:45:32 2012, masak wrote: > r: macro marco { AST.new }; marco > rakudo 6859fb: OUTPUT«===SORRY!===␤Error while compiling > block : Error while compiling op call: Error while compiling block : > Error while compiling block : Unknown QAST node type Any␤» > :> > diakopter: fair poi

[perl #75756] [BUG] Str.uc knows that the letter "ß" upper-cases "as "SS", case-insensitive regexes don't in Rakudo"

On Sat Oct 20 18:17:19 2012, coke wrote: > On Tue Jun 15 02:16:28 2010, masak wrote: > > How does case insensitive matching work in perl 6? > > e.g. "ß" ~~ m:i/SS/ > > sorear: that's the syntax, so I assume you're asking about the > > semantics. > > oh wait, that example is tricky :) > > I wo

[perl #101296] [BUG] Null PMC access when accessing type object belonging to an outer role from within an inner class in Rakudo

coke (>): > Is this sufficient to close the ticket? I would say so; the Null PMC access is gone. Resolving ticket.

[perl #74182] [TODO] Rakudo doesn't understand <-> pointy blocks

On Fri Apr 09 08:47:41 2010, masak wrote: > std: if 1 <-> $x {} > std 30351: OUTPUT«ok 00:01 107m␤» > rakudo: if 1 <-> $x {} > rakudo 4c94d7: OUTPUT«Missing block at line 11, near "" [...] > fejl > * masak submits rakudobug > rakudo: <-> $x { } > rakudo 4c94d7: OUTPUT«Confused at line 11, ne

[perl #115278] [BUG] Class B deriving from stubbed-and-then-defined class A doesn't have a .new method, nor a .gist method in Rakudo

I don't think you should be able to inherit from a class that's only stubbed the proper way is to stub the subclass I agree that the problem we're seeing here stems from deriving from the stubbed class. I'm not yet convinced it shouldn't be allowed. oh, TimToady++ has a fix in the backlog:

[perl #115272] [BUG] Totally legit thing inside <<...>> quotes deemed un-legit by Rakudo

rn: say <<'m'<\>'n'>> rakudo 8a07b8: OUTPUT«'m'<\>'n'␤» ..niecza v22-13-g0d2a99e: OUTPUT«'m'<>'n'␤» rn: say <'m'<\>'n'> niecza v22-13-g0d2a99e: OUTPUT«===SORRY!===␤␤Preceding context expects a term, but found infix < instead [...] Parse failed␤␤» ..rakudo 8a07b8: OUTPUT«'m'<>'n'␤» * masak de

[perl #114708] [BUG] LTA message when splicing into string

spider-mario (>): > sub test($x) {quasi {"$x"}} > > Result: > > > Error while compiling block : Error while compiling op call: Error while > compiling block : Error while compiling block test: Error while compiling > block : Error while compiling block : Unknown QAST node typ

[perl #114440] [BUG] 4 eqv 4.0 yields False in Rakudo

it is a nieczabug, not a rakudobug, since === and eqv can only match if the types are the same * masak rejects the rakudobug * masak submits nieczue

[perl #78276] [BUG] Null PMC access when calling a multi sub with a parameter narrowed by a subtype that does a regex match in Rakudo

r: sub detect(Str $foo where { /O/ }) {}; detect "O" rakudo 34e8d4: OUTPUT«No such method 'match' for invocant of type 'Any' [...] Oh...is that a sink context oopsie? r: subset Ostring of Str where { /O/ }; say "O" ~~ Ostring rakudo 34e8d4: OUTPUT«No such method 'match' for invocant of type

[perl #114276] [BUG] Cannot return junctions from .classify blocks in Rakudo

On Tue Aug 07 03:36:11 2012, moritz wrote: > What behavior do you expect? I can only fix it if I know what it should > look like after the fix :-) The immediate expectation is for the error "Cannot assign to a readonly variable or a value" not to occur. That's the observable -- sorry for being l

[perl #72326] [BUG] The same class-wide variable, accessed two different ways, behaves like two different variables in Rakudo

r: class A::B { my $c = 42; method foo { $A::B::c = "OH HAI"; say $c } }; A::B.foo rakudo 0eea68: OUTPUT«42␤» r: class A::B { my $c = 42; method foo { $c = "OH HAI"; say $A::B::c } }; A::B.foo rakudo 0eea68: OUTPUT«Any()␤» the former one is fine, I guess. at least if package stashes can be

  1   2   3   >