[02:52] *** [Coke] left
[03:01] <Geth> ¦ rakudo: ugexe++ created pull request #6483: RakuAST: late-bind qualified sub calls through the package chain

[03:01] <Geth> ¦ rakudo: review: https://github.com/rakudo/rakudo/pull/6483

[04:31] <Geth> ¦ rakudo: ugexe++ created pull request #6484: RakuAST: store an invokable attribute default as a value

[04:31] <Geth> ¦ rakudo: review: https://github.com/rakudo/rakudo/pull/6484

[04:35] *** coleman joined
[04:48] *** [Coke] joined
[05:27] *** apogee_ntv left
[05:53] *** nine left
[05:53] *** nine joined
[06:42] *** hurufu joined
[08:10] *** ShimmerFairy left
[08:11] *** ShimmerFairy joined
[08:35] *** hurufu left
[08:36] *** hurufu joined
[09:15] <Geth> ¦ rakudo/mention-gdb-plugin-in-rakudo-gdb-m-script: c19d06f170 | (Timo Paulssen)++ | tools/templates/moar/rakudo-debug-notice.in

[09:15] <Geth> ¦ rakudo/mention-gdb-plugin-in-rakudo-gdb-m-script: Explicitly mention the existence of the gdb python plugin

[09:15] <Geth> ¦ rakudo/mention-gdb-plugin-in-rakudo-gdb-m-script: 

[09:15] <Geth> ¦ rakudo/mention-gdb-plugin-in-rakudo-gdb-m-script: I've put some work into making the plugin work better and be more useful,

[09:15] <Geth> ¦ rakudo/mention-gdb-plugin-in-rakudo-gdb-m-script: so it could be good to point out that you may need to do one more thing

[09:15] <Geth> ¦ rakudo/mention-gdb-plugin-in-rakudo-gdb-m-script: to actually be able to use it when running rakudo-gdb-m on something:

[09:15] <Geth> ¦ rakudo/mention-gdb-plugin-in-rakudo-gdb-m-script: 

[09:15] <Geth> ¦ rakudo/mention-gdb-plugin-in-rakudo-gdb-m-script: Python plugins are only automatically loaded by gdb if they live in a path

[09:15] <Geth> ¦ rakudo/mention-gdb-plugin-in-rakudo-gdb-m-script: configured as "safe". Manually loading it from its full path can always be

[09:15] <Geth> ¦ rakudo/mention-gdb-plugin-in-rakudo-gdb-m-script: done with the `source` command which is also mentioned in the message.

[09:15] <Geth> ¦ rakudo/mention-gdb-plugin-in-rakudo-gdb-m-script: review: https://github.com/rakudo/rakudo/commit/c19d06f170

[09:15] <Geth> ¦ rakudo: timo++ created pull request #6485: Explicitly mention the existence of the gdb python plugin

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

[10:45] *** apogee_ntv joined
[11:43] <[Coke]> timo: note my comment on that PR. Safe to merge (when you fix masterduke's note) pre-release.

[11:44] <[Coke]> If you're going to squeeze it in, next few hours please.

[11:50] <timo> no, i won't

[11:50] <timo> squeeze it in, i mean

[11:53] <timo> ... or maybe it is actually fine this time? in that case i will make sure it works properly in the next minutes

[12:04] <timo> i just noticed that it also puts "running in the  debugger" which should have gdb or lldb in the middle there, that's a bug from before my pr though

[12:06] <Geth> ¦ rakudo/mention-gdb-plugin-in-rakudo-gdb-m-script: 9a33909d3c | (Timo Paulssen)++ | tools/templates/moar/rakudo-debug-notice.in

[12:06] <Geth> ¦ rakudo/mention-gdb-plugin-in-rakudo-gdb-m-script: Include an apostrophe in "gdb's"

[12:06] <Geth> ¦ rakudo/mention-gdb-plugin-in-rakudo-gdb-m-script: 

[12:06] <Geth> ¦ rakudo/mention-gdb-plugin-in-rakudo-gdb-m-script: It's a bit tricky since this gets expanded into a shell script where single

[12:06] <Geth> ¦ rakudo/mention-gdb-plugin-in-rakudo-gdb-m-script: quoted strings are a bit funny, and this code goes into such a single quoted

[12:06] <Geth> ¦ rakudo/mention-gdb-plugin-in-rakudo-gdb-m-script: string.

[12:06] <Geth> ¦ rakudo/mention-gdb-plugin-in-rakudo-gdb-m-script: review: https://github.com/rakudo/rakudo/commit/9a33909d3c

[12:25] <Geth> ¦ rakudo/main: c19d06f170 | (Timo Paulssen)++ | tools/templates/moar/rakudo-debug-notice.in

[12:25] <Geth> ¦ rakudo/main: Explicitly mention the existence of the gdb python plugin

[12:25] <Geth> ¦ rakudo/main: 

[12:25] <Geth> ¦ rakudo/main: I've put some work into making the plugin work better and be more useful,

[12:25] <Geth> ¦ rakudo/main: so it could be good to point out that you may need to do one more thing

[12:25] <Geth> ¦ rakudo/main: to actually be able to use it when running rakudo-gdb-m on something:

[12:25] <Geth> ¦ rakudo/main: 

[12:25] <Geth> ¦ rakudo/main: Python plugins are only automatically loaded by gdb if they live in a path

[12:25] <Geth> ¦ rakudo/main: configured as "safe". Manually loading it from its full path can always be

[12:25] <Geth> ¦ rakudo/main: done with the `source` command which is also mentioned in the message.

[12:25] <Geth> ¦ rakudo/main: review: https://github.com/rakudo/rakudo/commit/c19d06f170

[12:25] <Geth> ¦ rakudo/main: 9a33909d3c | (Timo Paulssen)++ | tools/templates/moar/rakudo-debug-notice.in

[12:25] <Geth> ¦ rakudo/main: Include an apostrophe in "gdb's"

[12:26] <Geth> ¦ rakudo/main: 

[12:26] <Geth> ¦ rakudo/main: It's a bit tricky since this gets expanded into a shell script where single

[12:26] <Geth> ¦ rakudo/main: quoted strings are a bit funny, and this code goes into such a single quoted

[12:26] <Geth> ¦ rakudo/main: string.

[12:26] <Geth> ¦ rakudo/main: review: https://github.com/rakudo/rakudo/commit/9a33909d3c

[12:26] <Geth> ¦ rakudo/main: 7d99efda5d | timo++ (committed using GitHub Web editor) | tools/templates/moar/rakudo-debug-notice.in

[12:26] <Geth> ¦ rakudo/main: Merge pull request #6485 from rakudo/mention-gdb-plugin-in-rakudo-gdb-m-script

[12:26] <Geth> ¦ rakudo/main: 

[12:26] <Geth> ¦ rakudo/main: Explicitly mention the existence of the gdb python plugin

[12:26] <Geth> ¦ rakudo/main: review: https://github.com/rakudo/rakudo/commit/7d99efda5d

[12:47] <[Coke]> Thanks.

[13:58] <Geth> ¦ rakudo: ugexe++ created pull request #6486: RakuAST: run a statement form try in a called thunk

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

[14:17] *** Sp1983 joined
[14:18] *** riaty joined
[14:18] *** riaty left
[14:27] *** Sp1983 left
[14:55] *** disbot1 joined
[15:08] *** Sp1983 joined
[15:22] *** Sp1983 left
[16:41] <Geth> ¦ rakudo: ugexe++ created pull request #6487: RakuAST: keep a traited variable reachable by name

[16:41] <Geth> ¦ rakudo: review: https://github.com/rakudo/rakudo/pull/6487

[17:12] <Geth> ¦ rakudo: ugexe++ created pull request #6488: RakuAST: report a public attribute call's own thunks

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

[18:25] *** hurufu1 joined
[18:25] *** hurufu left
[18:25] *** hurufu1 is now known as hurufu

[18:38] <[Coke]> releasable6: next

[18:38] <releasable6> [Coke], Next release is just a few moments away. There are no known blockers. 246 out of 249 commits logged

[18:38] <releasable6> [Coke], Details: https://gist.github.com/5d5c2eab68c22869b3cc2f1ab51c02cf

[18:54] <[Coke]> releasable6: next

[18:54] <releasable6> [Coke], Next release is just a few moments away. There are no known blockers. 249 out of 249 commits logged

[19:18] <Geth> ¦ rakudo: ugexe++ created pull request #6489: RakuAST: carry a dynamic regex's capture closures in its own frame

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

[19:40] <[Coke]> feeling a little meh, will probably try for release tomorrow morning.

[19:50] *** finanalyst joined
[20:11] <Geth> ¦ rakudo: ugexe++ created pull request #6490: RakuAST: anchor a qualified our-declaration at its leading package

[20:11] <Geth> ¦ rakudo: review: https://github.com/rakudo/rakudo/pull/6490

[21:14] <ugexe> oh wow, there is code in the legacy frontend made to specially handle modules that start with P5. i dont think we should do that in rakuast

[21:14] <ugexe> https://github.com/ugexe/rakudo/blob/4fb9c0dcb86a5907fd4e66ff8466c08bd39d5424/src/Perl6/World.nqp#L1417-L1422

[21:28] <ugexe> the comment here -- https://github.com/lizmat/P5tie/blob/4b06293bf373e27f46a561f3f148101dba88594b/lib/P5tie.rakumod#L35-L41 -- also alludes the module itself was written in a fragile way

[21:29] <ugexe> i wonder if we take that workaround logic from world and put it in P5tie's export if it would do the same thing

[21:32] *** hurufu left
[22:00] <lizmat> heh...  I guess jnthn sneaked that in at some point

[22:01] <lizmat> ugexe: I will check if moving the "use dynamic-scope" into P5tie  allows removing that hack

[22:05] <lizmat> yup: 88c46676c540eb39f74

[22:43] *** finanalyst left
[23:54] <ugexe> unfortunately i don't think the other p5 modules can be fixed

[23:56] <ugexe> for @a { chomp() } # this pattern specifically