From @masak

<diakopter> should try trap stub code executed?
<masak> rn​: try !!!; say "alive"
<p6eval> rakudo 2a41b3, niecza v24-35-g5c06e28​: OUTPUT«alive␤»
<masak> diakopter​: I don't see why not.
<diakopter> rn​: try ...; say "alive"
<p6eval> rakudo 2a41b3​: OUTPUT«Stub code executed␤current instr.​: 'throw' [...]
<p6eval> ..niecza v24-35-g5c06e28​: OUTPUT«alive␤»
<diakopter> rn​: try ???; say "alive"
<p6eval> rakudo 2a41b3​: OUTPUT«Stub code executed in block at
/tmp/fUkwbTNwFT​:1␤␤alive␤»
<p6eval> ..niecza v24-35-g5c06e28​: OUTPUT«alive␤»
<masak> I think neither ... nor ??? should emit anything.
<masak> aka Niecza is right twice.
* masak submits rakudobug

From @masak

<jnthn> ??? should warn.
<jnthn> ... should fail
<jnthn> The fail leaks out of the try
<jnthn> er, or either way the fail is in sink context
<jnthn> a fail in sink context throws.
<jnthn> ??? is correct in Rakudo
<jnthn> ... is debatable there; I think the current spec says that try
sinks everything inside of it, in which case it shoulda sunk, failed
inside the try, and been quiet.
* masak adds jnthn's comments to the ticket
<TimToady> try only sinks the inside if the outside is sunk, otherwise
it's eager
<jnthn> TimToady​: oh...
<jnthn> masak​: So seems it's just try ... that is in question in Rakudo,
not ??? :)
<masak> nod.
<masak> I'll change the bug title too.
<TimToady> S04​:1000
<jnthn> *nod*

@masak - Status changed from 'new' to 'open'

From @jnthn

On Mon Mar 18 13​:32​:39 2013, masak wrote​:

<diakopter> should try trap stub code executed?
<masak> rn​: try !!!; say "alive"
<p6eval> rakudo 2a41b3, niecza v24-35-g5c06e28​: OUTPUT«alive␤»
<masak> diakopter​: I don't see why not.
<diakopter> rn​: try ...; say "alive"
<p6eval> rakudo 2a41b3​: OUTPUT«Stub code executed␤current instr.​:
'throw' [...]
<p6eval> ..niecza v24-35-g5c06e28​: OUTPUT«alive␤»

This is now fixed, and tested in S04-statements/try.t.

@jnthn - Status changed from 'open' to 'resolved'