🦋 Welcome to the IRC channel of the core developers of the Raku Programming Language (raku.org #rakulang). This channel is logged for the purpose of history keeping about its development | evalbot usage: 'm: say 3;' or /msg camelia m: ... | Logs available at irclogs.raku.org/raku-dev/live.html | For MoarVM see #moarvm
Set by lizmat on 8 June 2022.
02:52 [Coke] left
Geth rakudo: ugexe++ created pull request #6483:
RakuAST: late-bind qualified sub calls through the package chain		 03:01
rakudo: ugexe++ created pull request #6484:
RakuAST: store an invokable attribute default as a value		 04:31
04:35 coleman joined 04:48 [Coke] joined 05:27 apogee_ntv left 05:53 nine left, nine joined 06:42 hurufu joined 08:10 ShimmerFairy left 08:11 ShimmerFairy joined 08:35 hurufu left 08:36 hurufu joined
Geth rakudo/mention-gdb-plugin-in-rakudo-gdb-m-script: c19d06f170 | (Timo Paulssen)++ | tools/templates/moar/rakudo-debug-notice.in
Explicitly mention the existence of the gdb python plugin

I've put some work into making the plugin work better and be more useful, so it could be good to point out that you may need to do one more thing to actually be able to use it when running rakudo-gdb-m on something:
Python plugins are only automatically loaded by gdb if they live in a path configured as "safe". Manually loading it from its full path can always be done with the `source` command which is also mentioned in the message.		 09:15
rakudo: timo++ created pull request #6485:
Explicitly mention the existence of the gdb python plugin
10:45 apogee_ntv joined
[Coke] timo: note my comment on that PR. Safe to merge (when you fix masterduke's note) pre-release. 11:43
If you're going to squeeze it in, next few hours please. 11:44
timo no, i won't 11:50
squeeze it in, i mean
... or maybe it is actually fine this time? in that case i will make sure it works properly in the next minutes 11:53
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:04
Geth rakudo/mention-gdb-plugin-in-rakudo-gdb-m-script: 9a33909d3c | (Timo Paulssen)++ | tools/templates/moar/rakudo-debug-notice.in
Include an apostrophe in "gdb's"

It's a bit tricky since this gets expanded into a shell script where single quoted strings are a bit funny, and this code goes into such a single quoted string.		 12:06
rakudo/main: c19d06f170 | (Timo Paulssen)++ | tools/templates/moar/rakudo-debug-notice.in
Explicitly mention the existence of the gdb python plugin

I've put some work into making the plugin work better and be more useful, so it could be good to point out that you may need to do one more thing to actually be able to use it when running rakudo-gdb-m on something:
Python plugins are only automatically loaded by gdb if they live in a path configured as "safe". Manually loading it from its full path can always be done with the `source` command which is also mentioned in the message.		 12:25
rakudo/main: 9a33909d3c | (Timo Paulssen)++ | tools/templates/moar/rakudo-debug-notice.in
Include an apostrophe in "gdb's"

It's a bit tricky since this gets expanded into a shell script where single quoted strings are a bit funny, and this code goes into such a single quoted string.
rakudo/main: 7d99efda5d | timo++ (committed using GitHub Web editor) | tools/templates/moar/rakudo-debug-notice.in
Merge pull request #6485 from rakudo/mention-gdb-plugin-in-rakudo-gdb-m-script

Explicitly mention the existence of the gdb python plugin
[Coke] Thanks. 12:47
Geth rakudo: ugexe++ created pull request #6486:
RakuAST: run a statement form try in a called thunk		 13:58
14:17 Sp1983 joined 14:18 riaty joined, riaty left 14:27 Sp1983 left 14:55 disbot1 joined 15:08 Sp1983 joined 15:22 Sp1983 left
Geth rakudo: ugexe++ created pull request #6487:
RakuAST: keep a traited variable reachable by name		 16:41
rakudo: ugexe++ created pull request #6488:
RakuAST: report a public attribute call's own thunks		 17:12
18:25 hurufu1 joined, hurufu left, hurufu1 is now known as hurufu
[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
[Coke], Details: gist.github.com/5d5c2eab68c22869b3...1ab51c02cf
[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
Geth rakudo: ugexe++ created pull request #6489:
RakuAST: carry a dynamic regex's capture closures in its own frame		 19:18
[Coke] feeling a little meh, will probably try for release tomorrow morning. 19:40
19:50 finanalyst joined
Geth rakudo: ugexe++ created pull request #6490:
RakuAST: anchor a qualified our-declaration at its leading package		 20:11
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
github.com/ugexe/rakudo/blob/4fb9c...1417-L1422
the comment here -- github.com/lizmat/P5tie/blob/4b062...od#L35-L41 -- also alludes the module itself was written in a fragile way 21:28
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:29
21:32 hurufu left
lizmat heh... I guess jnthn sneaked that in at some point 22:00
ugexe: I will check if moving the "use dynamic-scope" into P5tie allows removing that hack 22:01
yup: 88c46676c540eb39f74 22:05
22:43 finanalyst left
ugexe unfortunately i don't think the other p5 modules can be fixed 23:54
for @a { chomp() } # this pattern specifically 23:56

Powered by Cro and the Raku® Programming Language.

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

Thank you!