Spoke too soon. The issue is the Nil return type constraint. Golfed:
m: sub (-->Nil) { fail "{42}"; }()
rakudo-moar a09c8d: OUTPUT«Use of Nil in string context in sub at
line 1 in sub at line 1 in block at line
1Actually thrown at: in block at line 1»
On Thu Oct 13 18:31
PR merged[^1]; tests needed.
[1]
https://github.com/rakudo/rakudo/commit/7af9ec9d90d4ec8e9732e979729df85a80f7ec11
On Wed Oct 12 13:50:31 2016, david.warring wrote:
> I got this error from a typo in a large table. Needed to do a little
> work to find the problematic row.
>
> Have raised Rakudo
# New Ticket Created by Zoffix Znet
# Please include the string: [perl #129874]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=129874 >
Hm. Found a strange bug in core that I can't reproduce.
m: Bag.new-from-pairs: 1 => -1;
# New Ticket Created by Jan-Olof Hendig
# Please include the string: [perl #129860]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=129860 >
When running valgrind on t/04-nativecall/08-callbacks.t, a number of invalid
reads are
Am 11.10.2016 um 13:33 schrieb Steve Piner:
On Tue, 04 Oct 2016 04:23:54 +1300, Joachim Durchholz via RT
wrote:
Am 03.10.2016 um 06:34 schrieb Zoffix Znet via RT:
Seems the issue has more to do with running an empty loop, rather than
performing a real computation.
This is a run on a 4-core b
# New Ticket Created by cygx
# Please include the string: [perl #129855]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=129855 >
$ perl6 --version
This is Rakudo version 2016.09-169-ge2cd7a3 built on MoarVM version
20
