From zefram@fysh.org

"​:4\x[308]a".EVAL
Error encoding ASCII string​: could not encode codepoint 776

It seems correct for this to error, but this is not a clean error
signalled by the compiler. This is something inside the compiler barfing.

-zefram

From zefram@fysh.org

The behaviour has now changed to something different but also wrong​:

"​:4\x[308]a".EVAL
a => 0

It should yield either a syntax error or the same thing as "​:4a".
Given that "4\x[308]" is not being accepted as a digit in term context
or in Str.Int coercion, it should presumably yield a syntax error here.

-zefram

From @zoffixznet

On Tue, 05 Jul 2016 14​:22​:29 -0700, zefram@​fysh.org wrote​:

"​:4\x[308]a".EVAL
Error encoding ASCII string​: could not encode codepoint 776

It seems correct for this to error, but this is not a clean error
signalled by the compiler. This is something inside the compiler barfing.

-zefram

Thank you for the report. This is now fixed \o/

rakudo​: rakudo/rakudo@4663d43130
tests​: Raku/roast@b36289063e

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

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