00:04 iwuvmika joined 03:29 nine left, camelia left 03:30 nine joined 03:31 camelia joined 04:09 apogee_ntv left, apogee_ntv joined 05:05 shareable6 left 05:06 shareable6 joined 08:25 iwuvmika left
Geth rakudo/main: 73c915680c | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | 3 files
Make Int/Str/Num sorting up to 2.1x as fast (#6871)

  - Create Int/Str/Num sorting workers from a script
These private methods only differ in some minor nuances, so it makes sense to make these easily updatable in a builder script.
This also adds sorting logic for Num values only, as that was ... (19 more lines)		 09:23
rakudo/main: c5d06d2e47 | (Matt D)++ (committed using GitHub Web editor) | src/core.c/Proc.rakumod
fix: read %*ENV<COMSPEC> when %*ENV<ComSpec> is not present (MSYS2) (#6883)

MSYS2 exports COMSPEC instead of ComSpec.
shell() finds %*ENV<ComSpec> empty and exits with code -16 when invoked under MSYS2.
Resolves #6881		 09:26
rakudo/main: 2982e56ef2 | (Matt D)++ (committed using GitHub Web editor) | t/12-rakuast/strings.rakutest
Account for difference between windows cmd & POSIX shell behavior in deparser test (#6886)

Resolves #6884		 09:28
lizmat bisectable6: class Foo { has @.bar }; say Foo.new(|{:bar([1, 2, 3])}) 10:38
bisectable6 lizmat, Will bisect the whole range automagically because no endpoints were provided, hang tight
lizmat, ¦6c (105 commits): «Foo.new(bar => [[1, 2, 3],])␤» 10:39
lizmat, Nothing to bisect!
lizmat bisectable6: class A { has @.foo is rw = 42 }; my $a = A.new; my $b = $a.clone; $b.foo = 666; say $a.foo 11:25
bisectable6 lizmat, Will bisect the whole range automagically because no endpoints were provided, hang tight
lizmat, ¦6c (105 commits): «[666]␤» 11:26
lizmat, Nothing to bisect!
[Coke] nqp's opcode docs still talk about JS 13:22
lizmat I don't think the PR for that was merged, or even if there is a PR ? 13:24
[Coke] Was the PR for removing JS done? configure still lets you pick it. 13:32
ah, no, it's still there. :)
nevermind. :)
lizmat never got around figuring out the CI fails 13:35
Geth nqp/remove-js-backend: 20 commits pushed by (Elizabeth Mattijsen)++, (Nick Logan)++, (Patrick Böker)++, (Will Coleda)++, Faye++, MasterDuke17++
review: github.com/Raku/nqp/compare/627937...a983fd0a5b		 13:38
lizmat rebased and pushed
notable6__: weekly 13:55
notable6__ lizmat, 1 note: 2026-10-13T09:09:36Z <lizmat>: github.com/rakudo/rakudo/pull/6847
[Coke] Wonder if it's worth putting in a deprecated message into Configure.pl to warn folks it's going away 13:56
lizmat JS backend has been borked for years now ? 13:58
Geth rakudo/lizmat-93: 4 commits pushed by (Elizabeth Mattijsen)++, (Matt D)++ 14:12
[Coke] (borked) so, not worth it. Fair. 14:43
japhb On the plus side, Raku++ and Mutsu both have wasm backends 14:52
[Coke] Wonder if we want to lean in to "reference compiler" for rakudo 14:58
ShimmerFairy I've been thinking about the JS backend a bit, namely about if and how to deal with it when working on rakudo changes. My thinking has been that it'd make sense to replace it with a WASM backend, since I presume the point of the JS backend is to make web apps out of Raku; nowadays, you accomplish that by targeting WASM instead. 16:22
[Coke] I think pulling it out of rakudo makes sense at this point. 16:56
We have already demonstrated we don't have the bandwidth to support a 3rd backend (let alone a second)
ShimmerFairy That makes sense, my thinking can be summed up as "further work on the JS backend should be to replace it with WASM", but there could easily not be any further work in the first place. 17:01
fwiw I'm willing to start checking against the Java backend locally for whatever future changes I make, if that's not on the chopping block as well. I don't want to touch the JS backend though, simply because it appears to require touching npm. 17:03
[Coke] I would love to see some updates on the java backend if someone has the time. I think it's still functional enough that it doesn't make sense to remove that one. 17:10
ShimmerFairy That would be nice. I think it's good for nqp to have at least 2 backends, esp. one we don't control. I can't promise to take up the mantle there, but whenever I get back to doing more Unicode work I can at least check how the Java backend is handling that stuff. 17:44
lizmat ah, but please remember that the JVM doesn't have NFG afaik, or is that outdated information ? 17:55
I'm pretty sure the JS backend did not
ShimmerFairy I feel like it's the JS backend that tends to get excluded from various Unicode tests in the spec, but I'd have to double-check. 17:57
[Coke] I don't think NFG got written for java yet, no 18:05
But I also don't think we have CI for roast for anything, do we? (let alone java0
lizmat notable6__: weekly 18:11
notable6__ lizmat, 1 note: 2026-10-13T09:09:36Z <lizmat>: github.com/rakudo/rakudo/pull/6847
lizmat notable6__: weekly reset
notable6__ lizmat, Moved existing notes to “weekly_2026-10-26T18:11:04Z”
lizmat And yet another Raku Weekly hits the Net: rakuweekly.blog/2026/10/26/2026-42...iate-raku/ 18:32
ShimmerFairy I can't really get into it right this second, but I want to note that from a cursory glance that NQP's java dependencies in 3rdparty/ have mostly not been updated in a very long time; some of them have been sitting in their initial commits for 13 years! 18:44

Powered by Cro and the Raku® Programming Language.

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

Thank you!