[00:01] <ugexe> https://github.com/lizmat/P5chomp/blob/0dabc09e92f10edd1c8a4e4270bd1213835ecbdd/lib/P5chomp.rakumod#L123-L138 already foresaw this apparently

[00:59] <Geth> ¦ rakudo: ugexe++ created pull request #6492: RakuAST: install lowered array init after its operands evaluate

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

[04:25] *** vrurg joined
[04:25] *** vrurg_ left
[06:13] *** finanalyst joined
[07:26] <lizmat> ugexe: in the past I have been thinking about a trait that would allow having a subroutine be in charge of how it is generated in the AST

[07:26] <lizmat> so, this would allow in the "chomp" example to codegen it as .&chomp for instance

[07:28] <lizmat> sub chomp is ast(&foo)     where foo would receive the AST for the call, and be expected to return the ast that should be actually stored

[08:46] <lizmat> rakkable: eco-provides §macro

[08:46] <rakkable> lizmat, Running: eco-provides §macro, please be patient!

[08:46] <rakkable> lizmat, Found 130 lines in 45 files (30 distributions):

[08:46] <rakkable> lizmat, https://gist.github.com/ac6418eb10da58b2935fc5f51a161092

[08:53] <lizmat> looks like there's no actual "macro" use in the ecosystem anymore

[08:54] <lizmat> m: "use experimental :macros".AST.EVAL

[08:54] <camelia> rakudo-moar 6c5175469: ( no output )

[08:54] <lizmat> that feels LTA

[09:01] <lizmat> m: "acro".AST.EVAL

[09:01] <camelia> rakudo-moar 6c5175469: OUTPUT: «===SORRY!=== Error while compiling EVAL_0␤Undeclared routine:␤    acro used at line 1. Did you mean 'acro'?␤␤»

[09:01] <lizmat> did you mean acro ???

[09:58] <lizmat> why is it suggesting acro?  fwiw, other misspellings of "macro" do not show this suggestion

[11:10] *** camelia left
[11:13] *** camelia joined
[12:16] <timo> interesting, what does § do in rakkable?

[12:16] <timo> is it like "any sigil"?

[12:17] *** camelia left
[12:19] *** camelia joined
[12:53] *** liztormato joined
[12:53] <liztormato> It’s short for —type=word

[12:54] <timo> ah, neat. ok.

[12:54] <timo> I wonder how I can type that symbol easily on my keyboard

[12:54] <timo> compose + s + s gives ß, so not that

[12:56] <timo> with the new kde plasma feature where holding a key pops up a little palette of alternatives i can hold s and press 5 but at least in the terminal i also have to remove the initial s that got typed when i started holding the key :D

[13:02] *** liztormato left
[13:06] *** liztormato joined
[13:07] <liztormato> It’s standard on a Mac keyboard 

[13:10] *** liztormato left
[13:27] <timo> :)

[13:27] <timo> i have a very nonstandard keyboard anyway :D

[13:30] <[Coke]> releasable6: next

[13:30] <releasable6> [Coke], Next release will happen when it's ready. There are no known blockers. 249 out of 249 commits logged

[13:54] <Geth> ¦ rakudo/release-2026.07: 658f59bbcd | (Will Coleda)++ | tools/create-release-announcement.raku

[13:54] <Geth> ¦ rakudo/release-2026.07: Don't mention the mailing list.

[13:54] <Geth> ¦ rakudo/release-2026.07: review: https://github.com/rakudo/rakudo/commit/658f59bbcd

[13:54] <Geth> ¦ rakudo/release-2026.07: 2627fafa5a | (Will Coleda)++ | docs/release_guide.pod

[13:54] <Geth> ¦ rakudo/release-2026.07: Add explicit note about IGNORE section of wiki

[13:54] <Geth> ¦ rakudo/release-2026.07: review: https://github.com/rakudo/rakudo/commit/2627fafa5a

[13:54] <Geth> ¦ rakudo/release-2026.07: 422cf26900 | (Will Coleda)++ | 3 files

[13:54] <Geth> ¦ rakudo/release-2026.07: Update changelog + announcement

[13:54] <Geth> ¦ rakudo/release-2026.07: 

[13:54] <Geth> ¦ rakudo/release-2026.07: Deliberately not logged:

[13:54] <Geth> ¦ rakudo/release-2026.07: 

[13:54] <Geth> ¦ rakudo/release-2026.07: [773371d9][e4084e61][228e029c]

[13:54] <Geth> ¦ rakudo/release-2026.07: review: https://github.com/rakudo/rakudo/commit/422cf26900

[13:55] <[Coke]> Release announcement this release has collapsed all the rakuast items into a single line, doesn't share the commit IDs (those are all in the changelog still)

[14:00] <[Coke]> in future, we probably want to standardize on merge commits in all 3 repos for anything bigger than a single commit.

[14:00] <[Coke]> We've been doing that on rakudo for a few months, but not moarvm

[14:20] <[Coke]> MoarVM release done.

[14:20] <[Coke]> Will resume with nqp/rakudo in a while

[16:49] <timo> https://gist.github.com/timo/f2f8df64e7b58d3cdcd21735790df601

[17:07] <timo> ^- `moar hash` command in the gdb plugin spits out MVMStrHashTable contents, kind of like MVM_str_hash_fsck, but also works without a living process, and if anything is b0rked it won't segfault your process either

[17:19] <[Coke]> back from theoutside world

[17:41] <[Coke]> starting stress test.

[18:50] *** Geth joined
[18:51] *** lizmat joined
[19:58] *** lizmat left
[19:58] *** lizmat_ joined
[20:11] *** lizmat_ left
[20:11] *** lizmat joined
[20:12] <lizmat> [Coke]++ for yet another release!

[20:13] <lizmat> sorta missed that with all of the blackout issues here

[20:44] <Geth> ¦ nqp/main: 8bc6cdd718 | (Daniel Green)++ | tools/templates/MOAR_REVISION

[20:44] <Geth> ¦ nqp/main: Bump MoarVM for Ryu->Żmij switch

[20:44] <Geth> ¦ nqp/main: review: https://github.com/Raku/nqp/commit/8bc6cdd718

[20:49] <Geth> ¦ rakudo/main: c78d52e39d | (Daniel Green)++ | tools/templates/NQP_REVISION

[20:49] <Geth> ¦ rakudo/main: Bump NQP for Ryu->Żmij switch

[20:49] <Geth> ¦ rakudo/main: review: https://github.com/rakudo/rakudo/commit/c78d52e39d

[21:50] *** finanalyst left