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 '#`'
Opening bracket is required for #` comment at (eval) line 1:
According to S02 '#`' has to be followed by an opening bracket character: http://design.perl6.org/S02.html#Embedded_Comments
#Sat, 02 Dec 2017 05:42:24 -0800Aleks-Daniel Jakimenko-Aleksejev <firstname.lastname@example.org> - Subject changed from 'Rakudo allows using '#`' (embedded comment) without following opening bracket, should not' to '[@LARRY] Rakudo allows using '#`' (embedded comment) without following opening bracket, should not'
↑ 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, email@example.com wrote: Show quoted text
> 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
> On 2015-07-01 12:54:40, firstname.lastname@example.org 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 '#`'