[perl #111848] [BUG] The storage strategy for arrays is weird in Rakudo

2015-02-16 Thread Will Coleda via RT
On Sun Feb 10 02:05:54 2013, nicholas wrote: > On Mon Mar 19 11:34:12 2012, pmichaud wrote: > > The speed of Array vs. Hash element access is partially addressed by > > commit c10792f8. Before this commit, each Array element access via > > .at_pos($pos) resulted in an expensive call to self.exis

[perl #115276] [BUG] Here's a case where Niecza prints '4' but Rakudo gets confused about something

2015-02-16 Thread Will Coleda via RT
On Mon Oct 15 07:07:10 2012, masak wrote: > rn: say(|(|([4]))) > niecza v22-13-g0d2a99e: OUTPUT«4␤» > ..rakudo 8a07b8: OUTPUT«===SORRY!===␤CHECK FAILED:␤Undefined > routine '&prefix:<|>' called (line 1)␤» > * masak submits rakudobug > > diakopterbugs. they're weird and wonderful. :) Current be

[perl #117193] [BUG] Internal Parrot (imcc) error when trying to 'augment slang' on existing type in Rakudo

2015-02-16 Thread Will Coleda via RT
On Sun Mar 17 03:04:22 2013, masak wrote: > moritz: where would I find something about slangs in the synopsis? > probably S02 or so > ahh, found it http://perlcabal.org/syn/S02.html#Slangs > r: use MONKEY_TYPING; augment slang Regex { token numish { } }; > rakudo d98dd5: OUTPUT«use of uninitia

[perl #119293] Rakudo doesn't warn about Perl 5 $]

2015-02-16 Thread Will Coleda via RT
On Mon Oct 06 04:01:24 2014, barto...@gmx.de wrote: > Unfortunately the error message is only "Unexpected closing bracket" > now: > > 13:00 < bartolin> r: say $] > 13:00 <+camelia> rakudo-{parrot,moar} 65819d: OUTPUT«===SORRY!=== > Error while compiling /tmp/tmpfile␤Unexpected closing bracket␤at >

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

2015-02-16 Thread Will Coleda via RT
On Wed Sep 25 00:52:40 2013, masak wrote: > 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++ 01:09 < [Coke]> r: &&::{}[];; 01:09 <+camelia> rakudo-p

[perl #64990] Should be able to fail() from a upper-case-return-type-constrained sub in Rakudo

2015-02-16 Thread Will Coleda via RT
On Fri Mar 29 11:23:03 2013, coke wrote: > On Fri Aug 31 12:10:54 2012, moritz wrote: > > In nom, prefix and --> return type constraints weren't implemented for > > quite some time, which made the tests pass even though they shouldn't. > > Currently failure mode of tests: > > 14:21 < [Coke]> r: o

[perl #123570] [BUG] Two arithmetic expressions (involving addition, multiplication, division and modulo) which should come out the same come out different in Rakudo

2015-02-16 Thread Will Coleda via RT
On Fri Jan 09 06:47:29 2015, masak wrote: > r: say 6103515625/5; say 6103515625/5) * 4 + 123327057) ** > 2) % 6103515625); say (((1220703125 * 4 + 123327057) ** 2) % > 6103515625) > rakudo-{parrot,moar} c5dcdf: > OUTPUT«1220703125␤0␤6103515624␤» > ok -- between those three expressions, somet

[perl #77570] No protection against huge capture variables ($1, $2...) index

2015-02-16 Thread Will Coleda via RT
On Mon Feb 16 08:10:54 2015, Mouq wrote: > Seems to be okay now, even for larger numbers: > > 11:09 r: my $code = "\$" ~ 1 x 100; EVAL $code; say "alive" > 11:10 rakudo-{parrot,moar} f4379c: OUTPUT«alive␤» > > Marking as testneeded > > On Fri Mar 29 08:24:51 2013, coke wrote: > > On Thu De