[perl #119371] [BUG] Null PMC access when parameter mixes in role in macro in Rakudo

2014-11-09 Thread Christian Bartolomaeus via RT
This no longer leads to a Null PMC access on Parrot (the output is identical on Moar and JVM): $ perl6-p -e 'role popo { macro marco { $^a but popo }; marco popo; }' ===SORRY!=== Error while compiling -e None of the parametric role variants for 'popo' matched the arguments supplied. Cannot call '

[perl #122341] Unicode Character 'PARAGRAPH SEPARATOR' (U+2029) cannot be used to separate lines

2014-11-09 Thread Christian Bartolomaeus via RT
With the latest Parrot the tests pass on all backends again. I unfudged the tests with commit https://github.com/perl6/roast/commit/d6e7e47647 and I'm closing this ticket now.

[perl #123153] Assigning OUTER::OUTER::.keys() to a constant array generates an error

2014-11-09 Thread Christian Bartolomaeus via RT
This looks very similiar to Ticket #119521: https://rt.perl.org/Ticket/Display.html?id=119521 On Parrot we get a Null PMC access error with the same error message as in #119521: $ perl6-p -e 'constant @SOMETHING = OUTER::OUTER::.keys();' ===SORRY!=== Null PMC access in get_attr_str() If no one

[perl #111726] [BUG] Smartmatching an empty all-conjunction with a regex produces an internal unboxing error in Rakudo

2014-11-09 Thread Christian Bartolomaeus via RT
This looks related to the following two tickets: * https://rt.perl.org/Public/Bug/Display.html?id=120993 (~~ transforms junction into string before attempting to match) * https://rt.perl.org/Ticket/Display.html?id=112392 (resolved: .Str auto-threaded, meaning that it gave back another Junction,