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

# New Ticket Created by Sam S. # Please include the string: [perl #129114] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=129114 > This is how a state variable normally works: ➜ for ^2 { for ^2 { say (state $a)++ } }

[perl #129115] [BUG] loop doesn't allow the redeclaration of the symbol

# New Ticket Created by Itsuki Toyota # Please include the string: [perl #129115] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=129115 > See the following results. $ perl6 -e 'loop (my $foo;0;){}; loop (my $foo;0;){}' Potent

[perl #127933] [BUG][REPL] int# bug in REPL

Just a note: This seems to be a specific problem with Moar: $ ./perl6-j [...] > my int8 $i = 0x78; 120 > my int8 $j = 0x78; 120 > I'm going to tag this ticket with [MoarVM]. Or should the ticket be moved to the Github repo for MoarVM?

[perl #129020] [JVM] REPL does not work anymore: 'ContextRef representation does not implement elems'

On Thu Aug 25 22:25:10 2016, awwaiid wrote: > This is caused by RT#129092. > > Work-around submitted at https://github.com/rakudo/rakudo/pull/848. Thanks a lot! The tests in S19-command-line/repl.t are passing again. Since ticket #129092 (still open) targets the cause of the REPL failure, I'm c

Re: [perl #129088] [BUG] Error message provokes panic

> I think you're getting an end user's-eye view of what internal backtraces > look like. Right! If the problem is simply a user error, (an invalid entry in an sprintf format string), the messages are irrelevant and confusing. I thought I was reporting some problem in the processing or creation o

[perl #129115] [BUG] loop doesn't allow the redeclaration of the symbol

Not a bug, as S04 explains: Blocks are delimited by curlies, or by the beginning and end of the current compilation unit (either the current file or the current EVAL string). Unlike in Perl 5, there are (by policy) no implicit blocks aro

[perl #129120] [CONC] in await: Cannot invoke this object (REPR: Null; VMNull)

# New Ticket Created by Zoffix Znet # Please include the string: [perl #129120] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=129120 > On occasion, I get this error when trying to run the bellow program on a 32-core box: $