[perl #125621] Uncaught exceptions in Supply.tap are silenced

[via RT]

# New Ticket Created by  Rob Hoelz 
# Please include the string:  [perl #125621]
# in the subject line of all future correspondence about this issue. 
# URL: https://rt.perl.org/Ticket/Display.html?id=125621 


See the attached file.

The code in the attached file should make some indication that something in the 
code called provided to Supply.tap is going wrong, but the execution completes 
silently.

test.p6
Description: Binary data

[perl #125620] Exception subclasses without a message method aren't handled well by the top level exception handler

[via RT]

# New Ticket Created by  Rob Hoelz 
# Please include the string:  [perl #125620]
# in the subject line of all future correspondence about this issue. 
# URL: https://rt.perl.org/Ticket/Display.html?id=125620 


For example:

$ perl6 -e 'class CustomException is Exception {}; 
CustomException.new.throw'

This results in the following error output:

Unhandled exception: concatenate requires a concrete string, but got null
   at unknown:1  
(/home/rob/.mokudo/share/perl6/runtime/CORE.setting.moarvm:print_exception:4294967295)
 from src/gen/m-CORE.setting:15582  
(/home/rob/.mokudo/share/perl6/runtime/CORE.setting.moarvm:anon:43)
 from gen/moar/stage2/NQPHLL.nqp:1420  
(/home/rob/.mokudo/share/nqp/lib/NQPHLL.moarvm:command_eval:380)
 from src/Perl6/Compiler.nqp:59  
(/home/rob/.mokudo/share/nqp/lib/Perl6/Compiler.moarvm:command_eval:93)
 from gen/moar/stage2/NQPHLL.nqp:1360  
(/home/rob/.mokudo/share/nqp/lib/NQPHLL.moarvm:command_line:116)
 from src/gen/m-main.nqp:39  
(/home/rob/.mokudo/share/perl6/runtime/perl6.moarvm:MAIN:18)
 from src/gen/m-main.nqp:35  
(/home/rob/.mokudo/share/perl6/runtime/perl6.moarvm:mainline:197)
 from unknown:1  (/home/rob/.mokudo/share/perl6/runtime/perl6.moarvm:main:8)
 from unknown:1  
(/home/rob/.mokudo/share/perl6/runtime/perl6.moarvm:entry:9)

Adding a message method to CustomException causes the exception handler to 
print out more normal-looking output.

[perl #125616] Tapping stdout/stderr in Proc::Async on MoarVM doesn't close stdout/stderr pipes

[via RT]

# New Ticket Created by  Rob Hoelz 
# Please include the string:  [perl #125616]
# in the subject line of all future correspondence about this issue. 
# URL: https://rt.perl.org/Ticket/Display.html?id=125616 


See the attached test file.

If you tap standard output or standard error in Proc::Async, MoarVM sets up a 
pipe that doesn't seem to ever get closed.

test.p6
Description: Binary data

[perl #125618] Positional capture of separator on ?% operator causes compiler error

[via RT]

# New Ticket Created by  Faye 
# Please include the string:  [perl #125618]
# in the subject line of all future correspondence about this issue. 
# URL: https://rt.perl.org/Ticket/Display.html?id=125618 


ShimmerFairy m: say ab ~~ /^ a +% (b) $/
camelia rakudo-moar e4077e: OUTPUT«Nil␤»
ShimmerFairy m: say ab ~~ /^ a *% (b) $/
camelia rakudo-moar e4077e: OUTPUT«Nil␤»
ShimmerFairy m: say ab ~~ /^ a ?% (b) $/
camelia rakudo-moar e4077e: OUTPUT«===SORRY!===␤QAST::Block with cuid 
cuid_1_1436969557.11546 has not appeared␤»

On JVM:

ShimmerFairy j: say ab ~~ /^ a ?% (b) $/
camelia rakudo-jvm e4077e: OUTPUT«===SORRY!===␤setcodeobj can only be used 
with a CodeRef␤»

And just to show that it's not just the ?% operator alone contributing to the 
issue, but the capture too:

ShimmerFairy m: say ab ~~ /^ a ?% [b] $/
camelia rakudo-moar e4077e: OUTPUT«Nil␤»