From @bbkr

[14​:53] <bbkr> rakudo​: q\ \ # parsed as quoting
[14​:53] <p6eval> rakudo 5ae715​: ( no output )
[14​:53] <bbkr> std​: q\ \ # parsed as routine
[14​:53] <p6eval> std 32123​: OUTPUT«�[31m===�[0mSORRY!�[31m===�[0mâ�¤Undeclared
routine​:â�¤ 'q' used at line 1â�¤Check failedâ�¤FAILED 00​:01 114mâ�¤Â»
[14​:53] <bbkr> STD or Rakudo bug?
[14​:53] <bbkr> rakudo​: (q\ \).WHAT.say
[14​:53] <p6eval> rakudo 5ae715​: OUTPUT«Str()â�¤Â»
[14​:55] * moritz_ not sure

From @ShimmerFairy

Note that STD and Rakudo both agree on this working​:

<lue> std​: say q\hi\
<camelia> std d4cc5ab​: OUTPUT«ok 00​:00 42mâ�¤Â»
<lue> r​: say q\hi\
<camelia> rakudo b2072f​: OUTPUT«hiâ�¤Â»

Just be careful you don't use q\\ if you plan on using escape sequences​:

<lue> r​: say qq\hi \$a\
<camelia> rakudo b2072f​: OUTPUT«===SORRY!===â�¤Two terms in a rowâ�¤at
/tmp/HDCxB7aRCD​:1â�¤------> say qq\hi \â��$a\â�¤ expecting any of​:â�¤
postfix� infix stopper� infix or meta-infix�
statement end� statement modifier� statem�

<lue> std​: say qq\hi \$a\
<camelia> std d4cc5ab​: OUTPUT«===SORRY!===â�¤Two terms in a row at
/tmp/M7nKcfdtmv line 1​:â�¤------> say qq\hi \â��$a\â�¤ expecting any of​:â�¤
  POSTâ�¤ feed_separatorâ�¤ infix or meta-infixâ�¤ infixed functionâ�¤
  postcircumfixâ�¤ postfixâ�¤
<camelia> ..postfix_prefix_meta_operator� postop� s�

The RT System itself - Status changed from 'new' to 'open'

From @TimToady

I'm fine with the rakudo behavior here.

@TimToady - Status changed from 'open' to 'rejected'