From @masak

<masak> rn​: say <<<\>'n'>>
<p6eval> niecza v22-13-g0d2a99e​: OUTPUT«<>'n'␤»
<p6eval> ..rakudo 8a07b8​: OUTPUT«===SORRY!===␤Missing << or >>␤at
/tmp/rgRs_yIuEd​:1␤»
* masak submits rakudobug
<masak> motivation​: I think Niecza has it right here. thus, Rakudo has it wrong.

From @masak

<masak> rn​: say <<'m'<\>'n'>>
<p6eval> rakudo 8a07b8​: OUTPUT«'m'<\>'n'␤»
<p6eval> ..niecza v22-13-g0d2a99e​: OUTPUT«'m'<>'n'␤»
<masak> rn​: say <'m'<\>'n'>
<p6eval> niecza v22-13-g0d2a99e​: OUTPUT«===SORRY!===␤␤Preceding context
expects a term, but found infix < instead [...] Parse failed␤␤»
<p6eval> ..rakudo 8a07b8​: OUTPUT«'m'<>'n'␤»
* masak decides to include these discrepancies, also reported by
diakopter++, in the bug report

They seem relevant. The one who fixes the original bug may decide to
relate somehow to the above two discrepancies as well.

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

From @jnthn

On Mon Oct 15 06​:58​:31 2012, masak wrote​:

<masak> rn​: say <<<\>'n'>>
<p6eval> niecza v22-13-g0d2a99e​: OUTPUT«<>'n'␤»
<p6eval> ..rakudo 8a07b8​: OUTPUT«===SORRY!===␤Missing << or >>␤at
/tmp/rgRs_yIuEd​:1␤»
* masak submits rakudobug
<masak> motivation​: I think Niecza has it right here. thus, Rakudo has
it wrong.

No, Niecza gets it wrong too. Now Rakudo gets it righter than before,
and decidedly righter than Niecza​:

<<<\>'n'>>
<> n
<<<\>'n'>>.perl
("<>", "n")

<<...>> are shell words. The \> clearly must escape the >. And quotes in
shell words have meaning.

I think this is the right answer at last. :-)

/jnthn

From @moritz

Tested in S02-literals/quoting.t

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