On Mon, 12 Dec 2016 06:32:20 -0800, c...@zoffix.com wrote:
> Shows up in doc builds: https://travis-
> ci.org/perl6/doc/builds/183248892#L1224
>
> https://irclog.perlgeek.de/perl6/2016-12-12#i_13726254
>
> 14:30 jnthn The message does indicate a legit bug, but yes, the
> (harmless, just not c
Closable with rakudo tests then.
On 2018-01-06 12:59:07, jan-olof.hen...@bredband.net wrote:
> On Fri, 28 Jul 2017 15:52:53 -0700, timo wrote:
> > It could be that the commit i just pushed to moarvm fixes this,
> > please
> > verify (the code doesn't crash with the patch)
>
> Seems to work properl
On Fri, 28 Jul 2017 15:52:53 -0700, timo wrote:
> It could be that the commit i just pushed to moarvm fixes this, please
> verify (the code doesn't crash with the patch)
Seems to work properly:
dogbert@dogbert-VirtualBox ~/repos/rakudo $ ./perl6 -v
This is Rakudo version 2017.12-124-g6a6470f9d bu
On Wed, 06 Sep 2017 16:08:08 -0700, c...@zoffix.com wrote:
> IRC: https://irclog.perlgeek.de/perl6/2017-09-06#i_15127587
>
> Steps to repro. Create a file named "foo.p6" then run the following
> watcher in the directory and edit that file.
> The nofication reports a change in "foo.p6/foo.p6" inste
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 no
