More ways to trigger evalable

[AlexDaniel]

More ways to trigger evalable

[MasterDuke17]

I had another thought, anything that results in a "useless use of", also try the same thing with 'say ' in front and return both results.

[AlexDaniel]

This is exactly the reaction I was hoping for: https://irclog.perlgeek.de/perl6/2017-05-18#i_14599572

[AlexDaniel]

Maybe we should make it harder to trigger. Example: https://irclog.perlgeek.de/perl6/2017-09-05#i_15118238
The message in question actually looks like code. However, I've noticed that all times that we have evalable trigger on something we don't want to, it is always with non-zero exit code. So let's check the exit code before printing anything.

[AlexDaniel]

I think this can be closed. Would be great to have more tests though.

[AlexDaniel]

Leading space triggers both evalable and camelia: https://irclog.perlgeek.de/perl6/2018-02-03#i_15773390.

[AlexDaniel]

Somehow @jnthn++ is triggering evalable unintentionally, all the time.

<jnthn> m:g does multiple matches, and <( )> set the limits of the matching
<evalable6> jnthn, rakudo-moar 38afa2d6f: OUTPUT: «(exit code 1) ===SORRY!=== Error while compiling /tmp/O2Rtjzi3To␤Two ter…»
<evalable6> jnthn, Full output: https://gist.github.com/eea772e80efd46824cfd08cf7403a759
<jnthn> Oh, be quiet, evalable6 

<jnthn> | sleep &
<evalable6> jnthn,  rakudo-moar 890d628a2: OUTPUT: «Use of uninitialized value of type  Callable in numeric context␤ in block <unit> at /tmp/T…»
<evalable6> jnthn, Full output: https://gist.github.com/6233b79f46e6a3beb6420821bcce405a

These can be simply special-cased, I don't remember any other false positive.

[AlexDaniel]

I fixed it a little bit in a32bb60, but m:g is still triggering, so that should be special-cased too.