Ah. Now I see why. Consider this:
#`| foo | ↑ that does not DWIM. And it's right to assume that you can do it because s||| works just fine. So either it should understand stuff like this, or it can give an error message as todo-ed. So no, this is not rejectable. And the actual issue is about non-bracket characters, I think. On 2017-12-02 05:42:13, alex.jakime...@gmail.com wrote: > But why? “#` foo” looks like a fine normal comment, why should it > error out on > a perfectly normal behavior? > > I think this ticket is rejectable. Someone with bigger whatever should > reject > it. > > On 2015-07-01 12:54:40, barto...@gmx.de wrote: > > This ticket is about a failing test (fudged 'todo') in S32- > > exceptions/misc.t. Rakudo does not complain about a plain '#`', > > whereas STD does: > > > > $ perl6 -e '#`' > > $ viv -e '#`' > > ===SORRY!=== > > Opening bracket is required for #` comment at (eval) line 1: > > ------> #`⏏<EOL> > > Parse failed > > > > According to S02 '#`' has to be followed by an opening bracket > > character: http://design.perl6.org/S02.html#Embedded_Comments
