Geth rakudo: patrickbkr++ created pull request #3848:
Simplify binary release instructions a little		 08:43
lizmat Files=1334, Tests=113514, 225 wallclock secs (28.87 usr 8.78 sys + 3133.89 cusr 300.27 csys = 3471.81 CPU) 09:40
bisectable6: class Foo { has $!a = 42; method a { $!a }; method BUILD() { } }; dd Foo.new.a 09:56
bisectable6 lizmat, Will bisect the whole range automagically because no endpoints were provided, hang tight
lizmat, ¦6c (45 commits): «42␤»
lizmat, Nothing to bisect!
lizmat bisectable6: bisectable6: sub foo(:$bar, :$baz) { say “bar is $bar, $baz” }; foo:42bar:43baz 12:41
bisectable6 lizmat, Will bisect the whole range automagically because no endpoints were provided, hang tight
lizmat, ¦6c (45 commits): «bar is 42, 43␤» 12:42
lizmat, Nothing to bisect!
Geth ¦ rakudo: AlexDaniel self-assigned antipairs sub is not implemented github.com/rakudo/rakudo/issues/3782 22:09
Geth rakudo/sorting-with-junctions: d9c982b9a2 | (Elizabeth Mattijsen)++ | src/core.c/Rakudo/Sorting.pm6
Make error when sorting with junctions more awesome

You cannot sort a list that contains Junction values. The reason for this, is really that we do not have a sensible way of collapsing a Junction into an Order value.
Instead of dying with an internals error about not being able to coerce a Junction to an int, it now dies with a X::Cannot::Junction exception.
Spotted by AlexDaniel++		 22:41
rakudo: lizmat++ created pull request #3849:
Make error when sorting with junctions more awesome		 22:42

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!