From @masak

<lizmat> r​: say 100\ 000\ 000
<p6eval> ..rakudo ffe441​: OUTPUT«===SORRY!===␤Confused␤at
/tmp/YbI0EuDstU​:1␤------> say 100\ ⏏000\ 000␤expecting any
of​:␤unspace␤horizontal whitespace␤ postfix␤»
<lizmat> expecting any of​: unspace
<lizmat> but there is a an unspace there !
<lizmat> :-)
<masak> yeah, but after that :P
<masak> r​: "OH HAI"\ \ .say
<p6eval> rakudo ffe441​: OUTPUT«===SORRY!===␤Confused␤at
/tmp/GLc7SahIm9​:1␤------> "OH HAI"\ ⏏\ .say␤ expecting any
of​:␤unspace␤horizontal whitespace␤postfix␤»
<masak> *that*, however...
* masak submits rakuodbug

So, my complaint (and lizmat's) is that Rakudo says it expects unspace
in the error message, when unspace is what it (correctly) chokes on.

From @peschwa

Am Mi 03. Apr 2013, 14​:13​:36, masak schrieb​:

<lizmat> r​: say 100\ 000\ 000
<p6eval> ..rakudo ffe441​: OUTPUT«===SORRY!===␤Confused␤at
/tmp/YbI0EuDstU​:1␤------> say 100\ ⏏000\ 000␤expecting any
of​:␤unspace␤horizontal whitespace␤ postfix␤»
<lizmat> expecting any of​: unspace
<lizmat> but there is a an unspace there !
<lizmat> :-)
<masak> yeah, but after that :P
<masak> r​: "OH HAI"\ \ .say
<p6eval> rakudo ffe441​: OUTPUT«===SORRY!===␤Confused␤at
/tmp/GLc7SahIm9​:1␤------> "OH HAI"\ ⏏\ .say␤ expecting any
of​:␤unspace␤horizontal whitespace␤postfix␤»
<masak> *that*, however...
* masak submits rakuodbug

So, my complaint (and lizmat's) is that Rakudo says it expects unspace
in the error message, when unspace is what it (correctly) chokes on.

Fixed in rakudo PR #​250, added test to roast in commit 9801c79 as per the example above.

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

From @usev6

As the tests in S02-lexical-conventions/unspace.t run fine, I'm closing this ticket.

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