[02:37] <Geth> ¦ rakudo: farisbasha++ created pull request #6938: Fix the dead #raku-dev IRC log link in CONTRIBUTING

[02:37] <Geth> ¦ rakudo: review: https://github.com/rakudo/rakudo/pull/6938

[05:52] *** hurufu joined
[05:54] *** hurufu left
[05:55] *** hurufu joined
[07:24] *** hurufu left
[07:26] *** hurufu joined
[08:24] *** hurufu left
[08:25] *** hurufu joined
[09:03] <Geth> ¦ rakudo/main: e3613c0d12 | (Faris Basha TM)++ (committed using GitHub Web editor) | CONTRIBUTING.md

[09:03] <Geth> ¦ rakudo/main: Fix the dead #raku-dev IRC log link in CONTRIBUTING (#6938)

[09:03] <Geth> ¦ rakudo/main: 

[09:03] <Geth> ¦ rakudo/main: The colabti.org irclogger page for #raku-dev now returns 404. Link to

[09:03] <Geth> ¦ rakudo/main: the #raku-dev logs on irclogs.raku.org instead.

[09:03] <Geth> ¦ rakudo/main: review: https://github.com/rakudo/rakudo/commit/e3613c0d12

[09:24] <lizmat> argh... looks like b0be8005a74 broke the JVM build

[09:24] <linkable6> (2026-11-15) https://github.com/rakudo/rakudo/commit/b0be8005a7 Simplify some container/attribute logic (#6914)

[09:25] <lizmat> which I guess also means that 2026.11 does not build on JVM  :-(

[09:25] <lizmat> which in turn breaks NQP CI  

[09:26] <Geth> ¦ rakudo/lizmat-136: 34a5e1501c | (Elizabeth Mattijsen)++ | src/Perl6/bootstrap.c/BOOTSTRAP.nqp

[09:26] <Geth> ¦ rakudo/lizmat-136: Hopefully unbreak the JVM build

[09:26] <Geth> ¦ rakudo/lizmat-136: 

[09:26] <Geth> ¦ rakudo/lizmat-136: Introduced by b0be8005a74

[09:26] <Geth> ¦ rakudo/lizmat-136: review: https://github.com/rakudo/rakudo/commit/34a5e1501c

[09:27] <Geth> ¦ rakudo: lizmat++ created pull request #6939: Hopefully unbreak the JVM build

[09:27] <Geth> ¦ rakudo: review: https://github.com/rakudo/rakudo/pull/6939

[09:28] <lizmat> I guess this also implies the JVM backend is close to death  :-(    nobody noticed it not building

[10:04] <lizmat> Otoh, by the looks of https://github.com/Raku/nqp/pull/872 , the JVM build was already broken on Sep 7, possibly going back to before May 11

[10:04] *** hurufu left
[10:05] <lizmat> possibly even before that, as it looks like before Nov 9, 2025 the JVM was not in NQP's CI

[10:13] *** hurufu joined
[10:50] <refactus> on one hand I think about all the extra work we've done to keep things working on jvm and try to maintain some sembalance of feature parity, and it seems like it'd be a shame and a waste to throw it all away. on the other hand I think about all the extra work we've done to continue supporting a backend that almost nobody has used since moar was developed, and it seems like a bit of a shame and a

[10:50] <refactus> waste to keep doing it

[11:02] <lizmat> https://en.wikipedia.org/wiki/Sunk_cost

[11:03] <lizmat> :-(

[11:04] *** hurufu left
[11:05] <apogee_ntv> I think the main use I would have for JVM backend (can't speak for anyone else) is being able to target Android.

[11:05] *** hurufu joined
[11:05] <apogee_ntv> Dont know if thats doable or close or far off

[11:05] <lizmat> which raku++ now covers, fwiw

[11:05] <apogee_ntv> Interesting

[11:06] <lizmat> yeah, the world is changing

[11:06] <apogee_ntv> It's changing fast

[11:17] <refactus> I know the last time I tried to fudge a test under jvm for a feature I implemented, someone here was still using it and helped me try to make it work, but I guess that was several years ago now. don't even recall who it was

[11:39] <refactus> it was usev6. https://github.com/Raku/nqp/issues/727 was what I ran into. half a decade ago. but yes, sunk cost fallacy, I agree. it does kinda look that way if it's been broken for months and nobody reported it

[11:42] <lizmat> oddly enough, the rakudo CI is green on my PR

[11:43] <lizmat> which includes JVM builds

[11:44] <lizmat> so I wonder what's going on here, maybe there's an issue with  the NQP CI creating false negatives

[11:45] <lizmat> someone with more Azure CI chops should have a look at https://github.com/Raku/nqp/blob/main/azure-pipelines.yml then, japhb ?

[11:50] <Geth> ¦ rakudo/main: a364d455f0 | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | src/Perl6/bootstrap.c/BOOTSTRAP.nqp

[11:50] <Geth> ¦ rakudo/main: Unbreak the JVM build (#6939)

[11:50] <Geth> ¦ rakudo/main: 

[11:50] <Geth> ¦ rakudo/main: Introduced by b0be8005a74

[11:50] <Geth> ¦ rakudo/main: review: https://github.com/rakudo/rakudo/commit/a364d455f0

[13:05] *** hurufu left
[13:05] *** hurufu1 joined
[13:07] *** hurufu1 is now known as hurufu

[13:29] <[Coke]> Next scheduled release date is the day after Christmas.

[13:29] <[Coke]> I am *fine* with no release next month.

[14:51] *** MasterDuke joined
[15:08] *** MasterDuke left
[15:35] *** hurufu left
[16:59] <Geth> ¦ rakudo/lizmat-137: c8558383f8 | (Elizabeth Mattijsen)++ | 6 files

[16:59] <Geth> ¦ rakudo/lizmat-137: RakuAST: change ::Origins interface to use positionals

[16:59] <Geth> ¦ rakudo/lizmat-137: 

[16:59] <Geth> ¦ rakudo/lizmat-137: The RakuAST::Origins.new method is basically called for each

[16:59] <Geth> ¦ rakudo/lizmat-137: RakuAST element that is generated from source, so that is a *lot*.

[16:59] <Geth> ¦ rakudo/lizmat-137: 

[16:59] <Geth> ¦ rakudo/lizmat-137: However, the number of places where it is being called, are few

[16:59] <Geth> ¦ rakudo/lizmat-137: and in the core only.  So it makes sense to use the slightly cheaper

[16:59] <Geth> ¦ rakudo/lizmat-137: way of using positional argments instead of named arguments.

[16:59] <Geth> ¦ rakudo/lizmat-137: 

[17:00] <Geth> ¦ rakudo/lizmat-137: This also needed changing 1 test that was actually testing the

[17:00] <Geth> ¦ rakudo/lizmat-137: internal interface.

[17:00] <Geth> ¦ rakudo/lizmat-137: review: https://github.com/rakudo/rakudo/commit/c8558383f8

[17:00] <Geth> ¦ rakudo: lizmat++ created pull request #6940: RakuAST: change ::Origins interface to use positionals

[17:00] <Geth> ¦ rakudo: review: https://github.com/rakudo/rakudo/pull/6940

[17:03] *** hurufu joined
[17:45] *** hurufu left
[17:46] *** hurufu joined
[18:30] *** hurufu left
[18:38] *** hurufu joined
[18:58] <Geth> ¦ rakudo/lizmat-138: 6f4fc8674e | (Elizabeth Mattijsen)++ | src/Raku/ast/base.rakumod

[18:58] <Geth> ¦ rakudo/lizmat-138: RakuAST: introduce RAKUDO_OPTIMIZE_DEBUG env variable

[18:58] <Geth> ¦ rakudo/lizmat-138: 

[18:58] <Geth> ¦ rakudo/lizmat-138: Shows the result of static optimizations (the "optimize" stage)

[18:58] <Geth> ¦ rakudo/lizmat-138: on STDERR.  The value specified is the name of the method that

[18:58] <Geth> ¦ rakudo/lizmat-138: should be used to represent the before/after stage of the

[18:58] <Geth> ¦ rakudo/lizmat-138: of the optimization.  So with "DEPARSE"

[18:58] <Geth> ¦ rakudo/lizmat-138: 

[18:58] <Geth> ¦ rakudo/lizmat-138: <…commit message has 17 more lines…>

[18:58] <Geth> ¦ rakudo/lizmat-138: review: https://github.com/rakudo/rakudo/commit/6f4fc8674e

[18:58] <Geth> ¦ rakudo: lizmat++ created pull request #6941: RakuAST: introduce RAKUDO_OPTIMIZE_DEBUG env variable

[18:58] <Geth> ¦ rakudo: review: https://github.com/rakudo/rakudo/pull/6941

[19:06] <Geth> ¦ rakudo/lizmat-139: d26ba2f3fd | (Elizabeth Mattijsen)++ | src/Raku/ast/base.rakumod

[19:06] <Geth> ¦ rakudo/lizmat-139: RakuAST: reduce conditions for each optimizing recursion

[19:06] <Geth> ¦ rakudo/lizmat-139: 

[19:06] <Geth> ¦ rakudo/lizmat-139: Instead of storing the conditions in variables, and then checking

[19:06] <Geth> ¦ rakudo/lizmat-139: them 4 times, use the conditions to set up an if/elsif/else

[19:06] <Geth> ¦ rakudo/lizmat-139: structure with just the calls needed.

[19:06] <Geth> ¦ rakudo/lizmat-139: review: https://github.com/rakudo/rakudo/commit/d26ba2f3fd

[19:07] <Geth> ¦ rakudo: lizmat++ created pull request #6942: RakuAST: reduce conditions for each optimizing recursion

[19:07] <Geth> ¦ rakudo: review: https://github.com/rakudo/rakudo/pull/6942

