On Sat, 07 Jan 2017 11:33:55 -0800, gfldex wrote:
> sub postcircumfix:«> <»($a){}; loop (my $i=0;$i>10;$i++) {};
>
> # OUTPUT«===SORRY!=== Error while compiling <tmp>Unable to parse
> expression in postcircumfix:sym«> <»; couldn't find final $stopper at
> <tmp>:1------> rcumfix:«> <»($a){}; loop (my $i=0;$i>10⏏;$i++) {};
> expecting any of: s…»
>
> # `final $stopper` should say `<`
>From the perspective of the guts behind it, this behavior is correct,
as vars in rx "do not interpolate" and the rx engine resolves them
later when needed. In a situation where you were using these guts and
passed them a terminator in a variable, you'd want the error message
to tell you what variable you passed it in with.
However, since the particular case here is used as an example in S05, and
it is only the way rakudo chose to use those guts internally that causes this
deviation, it was worth bodging around.
Fix committed in rakudo 909688953.
Tests commited in roast 2cef80a32.
Closing.
