From @bbkr

[15​:31] <bbkr> std​: _*.A
[15​:31] <p6eval> std 31912​: OUTPUT«�[31m===�[0mSORRY!�[31m===�[0mâ�¤Undeclared
name​:â�¤ '_' used at line 1â�¤Check failedâ�¤FAILED 00​:01 114mâ�¤Â»
[15​:31] <bbkr> rakudo​: _*.A
[15​:31] <p6eval> rakudo bef86e​: ( no output )
[15​:32] <bbkr> should example above be reported?
[15​:32] <masak> if you can explain to us what it does. :)
[15​:33] <moritz_> it calls a routine
[15​:33] <moritz_> called _
[15​:33] <masak> rakudo​: _~*.A; say "alive"
[15​:33] <p6eval> rakudo bef86e​: OUTPUT«aliveâ�¤Â»
[15​:33] <moritz_> with an argument that is a curried, stringied method call
[15​:33] <moritz_> you know *.A
[15​:33] <masak> why is &_ defined?
[15​:33] <moritz_> it shouldn't be
[15​:33] <bbkr> exactly, why?
[15​:33] <moritz_> rakudo​: _; say "alive"
[15​:33] <masak> bbkr​: there's your bug.
[15​:33] <p6eval> rakudo bef86e​: OUTPUT«Could not find sub &_â�¤ in main program
body at line 22​:/tmp/4p240eNSrSâ�¤Â»
[15​:34] <bbkr> hmm
[15​:34] <bbkr> rakudo​: _1; say "alive"
[15​:34] <p6eval> rakudo bef86e​: OUTPUT«Could not find sub &_â�¤ in main program
body at line 22​:/tmp/9xgRgdcVYmâ�¤Â»
[15​:34] <masak> ooh! the whole thing is curried, and thus never run!
[15​:34] <masak> of course!
[15​:34] <moritz_> but how is it parsed?
[15​:34] <moritz_> as _() ~ *.A?
[15​:34] <masak> moritz_​: rakudo doesn't check for undeclared sub names.
[15​:35] <masak> moritz_​: aye.
[15​:35] <moritz_> but it shouldn't
[15​:35] <moritz_> should be _(*.A), afaict
[15​:35] <masak> oh.
[15​:35] <masak> then that's the bug. :)
[15​:35] <-- tadzik has left this server (Ping timeout​: 252 seconds).
[15​:35] <moritz_> because unknown identifiers should be treated as listops
[15​:35] <moritz_> no?
[15​:35] <moritz_> bbkr​: have fun composing that ticket :-)
[15​:36] <masak> just copy all we say into it :)
[15​:36] <masak> moritz_​: as far as I know, you're right.
[15​:36] <masak> about the listops thing.

From @FROGGS

same like std now​:

<FROGGS> rakudo​: _~*.A
<p6eval> rakudo bf472b​: OUTPUT«===SORRY!===â�¤CHECK FAILED​:â�¤Undefined
routine '&_' called (line 1)�»

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

From @coke

On Wed Nov 21 08​:31​:03 2012, FROGGS.de wrote​:

same like std now​:

<FROGGS> rakudo​: _~*.A
<p6eval> rakudo bf472b​: OUTPUT«===SORRY!===â�¤CHECK FAILED​:â�¤Undefined
routine '&_' called (line 1)�»

... So, closable with tickets, thanks!
--
Will "Coke" Coleda

From @coke

On Wed May 29 19​:38​:02 2013, coke wrote​:

On Wed Nov 21 08​:31​:03 2012, FROGGS.de wrote​:

same like std now​:

<FROGGS> rakudo​: _~*.A
<p6eval> rakudo bf472b​: OUTPUT«===SORRY!===â�¤CHECK FAILED​:â�¤Undefined
routine '&_' called (line 1)�»

... So, closable with tickets, thanks!

For lack of a better placed, added to integration/weird_errors.t
--
Will "Coke" Coleda

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