01:05 sivoais left, sivoais_ joined
timo1 anyone interested in adding support for some IRCv3 features to our IRC modules? :D 11:03
Geth rakudo/lizmat-split-enz: af6250d86f | (Elizabeth Mattijsen)++ | src/core.c/Str.rakumod
Add :end named argument to .split with limit

As discussed at
   irclogs.raku.org/raku/2026-02-11.h...18:33-0001
The implementation is really just a post-processing wrapper around the basic implementation`. For some reason it also needed two multi candidates, because otherwise the :end! candidates wouldn't get selected.
11:05
rakudo: lizmat++ created pull request #6072:
Add :end named argument to .split with limit
rakudo/main: 7cbf36b50e | (Will Coleda)++ (committed using GitHub Web editor) | src/core.c/IO/Handle.rakumod
Fix typo in error (#6069)

  * Fix typo in error
  * prefer spelling found in Raku/doc repo
11:09
11:17 librasteve_ joined 12:03 timo1 is now known as timo 12:09 [TuxCM] joined 12:16 [TuxCM] left 12:17 [TuxCM] joined 12:48 [TuxCM] left 12:50 |Tux| joined
Geth ¦ rakudo: coke self-assigned Match method doesn't work properly with the :pos parameter github.com/rakudo/rakudo/issues/5982 13:46
¦ rakudo: coke self-unassigned Match method doesn't work properly with the :pos parameter github.com/rakudo/rakudo/issues/5982 13:47
[Coke] (oops)
14:06 librasteve_ left 15:18 librasteve_ joined 15:19 |Tux| left
Geth rakudo/main: 6acaa900d1 | (Elizabeth Mattijsen)++ | 7 files
Micro-opt self.CREATE -> nqp::create(self)

This saves an nqp::hllize and nqp::decont in bytecode, but these would be removed anyways by spesh. So questionable as an opt, but at least it makes the use consistent in core (as there are
  *many* nqp::create calls in core, but only a few .CREATE ones)
17:43
japhb lizmat++ # Consistency 17:44
lizmat talking about consistency: 19:54
m: class A { method FALLBACK($name, |c) { dd $name } }; class B is A { }; B.foobar
camelia "foobar"
lizmat so, that's to be expected
m: class A { submethod FALLBACK($name, |c) { dd $name } }; class B is A { }; B.foobar
camelia "foobar"
lizmat I sorta expected that to fail
because of the submethod 19:55
was I wrong ?
bisectable6: class A { submethod FALLBACK($name, |c) { dd $name } }; class B is A { }; B.foobar
bisectable6 lizmat, Will bisect the whole range automagically because no endpoints were provided, hang tight
lizmat, Output on all releases: gist.github.com/e787a354b83f6188ce...622ac23f63 19:56
lizmat, Bisecting by exit code (old=2022.06 new=2022.07). Old exit code: 1
lizmat, bisect log: gist.github.com/97907af9eac2a26871...3a8574eff9 19:58
lizmat, Bisecting by output (old=2016.09 new=2016.10) because on both starting points the exit code is 1
lizmat, bisect log: gist.github.com/63d4ebdfdf33baaf10...02dd8faf99 19:59
lizmat, Output on all releases and bisected commits: gist.github.com/d8446d052a58242682...3dc300e477
lizmat bisectable6: old=2022.06 new=2022.07 class A { submethod FALLBACK($name, |c) { dd $name } }; class B is A { }; B.foobar 20:02
bisectable6 lizmat, Bisecting by exit code (old=2022.06 new=2022.07). Old exit code: 1
lizmat, bisect log: gist.github.com/2d562b1aa5de10505b...a506e229a6 20:04
lizmat, There are 33 candidates for the first “new” revision. See the log for more details
lizmat well... that's pretty confusing :-) 20:07
nemokosch oh, callback is like __get in PHP 20:53
*FALLBACK, even