[01:45] *** hulk joined [01:46] *** kylese left [01:53] *** lizmat left [02:03] *** johnjay joined [02:15] *** hulk left [02:15] *** kylese joined [03:18] *** ckfl3266 left [05:28] *** Sgeo left [05:54] *** belluzj joined [07:08] *** belluzj left [07:36] *** lizmat_ left [07:37] *** lizmat joined [07:56] *** dakkar joined [08:44] quit [08:44] *** grondilu left [08:45] *** rnddim joined [08:46] *** rnddim left [08:46] *** ShimmerFairy left [08:46] *** rnddim joined [08:49] *** rnddim left [08:50] *** rnddim joined [08:50] *** rnddim left [08:51] *** rnddim joined [09:19] *** vasko453558616 left [09:38] *** vasko453558616 joined [09:52] *** rnddim is now known as ShimmerFairy [13:01] *** Sgeo joined [13:24] *** japhb left [13:49] The first Raku Weekly News hits the Net: https://rakuweekly.blog/2026/10/05/2026-40-pythonesque/ [14:12] @lizmat "Math::NIntegrate" was not mentioned... 😭 [14:12] that was mentioned last week? [14:13] ah, I missed an update, sorry :-) [14:13] I updated it twice in the last few days. It is not a big deal. I plan to publish a blog post about it soon. [14:14] updated [14:14] BTW, there is also raptor, to keep company of Raku++ and mitsu. [14:15] I mention raptor just for reference, not saying that it has to be included in the blog post. [14:16] yeah... I don't see that as a full Raku implementation [14:16] more as a language that stole some ideas from Raku [14:18] *borrowed [14:18] :-) [14:18] Yeah, but it has motivation that inspired a few discussions... I am still not sure that the motivation is (very) valid, hence, discussions and blah, blah. [14:19] *Also, "mutsu", not "mitsu" (soup). [14:20] (In my message above.) [14:20] ah, *phew* thought I wrote it wrong in the weekly :-) [14:21] @lizmat Is there any way to get the code behind a Callable? Say, from -> $x { $x.sqrt}. [14:22] Are there any plans in the future to be able to do that? [14:24] hmm... if you know where the Callable lives, you could look it up in $?SOURCE ? [14:25] I can examine $?SOURCE inside the callable? [14:25] m: say $?SOURCE [14:25] rakudo-moar e17a1d43b: OUTPUT: «say $?SOURCE␤» [14:26] m: say $?SOURCE; # this is a comment [14:26] rakudo-moar e17a1d43b: OUTPUT: «say $?SOURCE; # this is a comment␤» [14:26] I guess the line granularity is not enough [14:26] Yeah, just tried that. [14:27] Interesting, though. I did not know about $?SOURCE. [14:55] * [Coke] wonders if japhb has a sample somewhere of printing a data structure every interval that briefly highlights when something changed since the last print. [14:58] tbrowder: yeah, githun has some trouble with the debian 11 and opensuse tumbleweed repos [14:58] github [14:59] *** El_Che left [14:59] I noticed that earlier today, I cannot retrieve certain packages/ files from GitHub. [15:00] *** El_Che joined [15:09] *** japhb joined [15:18] hm, i have debian 13 trixie and no update yet [15:21] yeah, they are all built by the same process [15:22] once they all pass, the build is tagged, rebuilt and uploaded [15:23] re-running now in the hope the github problems are gone [15:25] I'll remove support for debian 11, it's EOL anyway [16:32] *** dakkar left [16:41] I'll temporarily disable tumbleweed because their repo in broken atm (in flux) [16:42] then the rest of the packages can be uploaded [17:32] *** belluzj joined [17:34] *** belluzj left [17:53] *** lucerne90 joined [18:01] *** ugexe left [18:04] *** ugexe joined [18:28] *** lucerne90 left [18:34] *** lucerne90 joined [19:01] *** lucerne90 left [19:41] *** mc2 joined [19:41] hi everyone [19:57] <[Coke]> hi [20:07] *** hurufu joined [20:17] E? [20:44] oh wow, raku weekly, nice [20:46] * [Coke] wonders if the other rakudo compilers will get somethig like committable so they can be run through blin [20:46] <[Coke]> s/do// [20:46] [Coke], rakudo-moar 88626a34b: OUTPUT: «Use of uninitialized value $_ of type Any in string context.␤Methods .^name, .raku, .gist, or .say can be used to stringify it to something meaningful.␤ in block at /tmp/AC5CRDX46i line 1␤» [20:47] <[Coke]> evalable6: bite me [20:47] [Coke], rakudo-moar 88626a34b: OUTPUT: «(exit code 1) ===SORRY!=== Error while compiling /tmp/Nds0gBTSh8␤Undeclared routines:␤ bite used at line 1␤ me used at line 1␤␤» [21:00] *** jargan joined [21:02] *** tobs` joined [21:02] *** rnddim joined [21:02] *** notable6__ joined [21:04] *** lucs_ joined [21:05] *** jdv_ joined [21:07] *** camelia left [21:07] *** notable6 left [21:07] *** jast left [21:07] *** tobs left [21:07] *** ShimmerFairy left [21:07] *** lucs left [21:07] *** jdv left [21:07] *** tobs` is now known as tobs [21:22] *** camelia joined [21:38] *** hurufu left [22:51] [Coke]: I had gotten knocked offline earlier, but I just say this in the backlog: [Coke] wonders if japhb has a sample somewhere of printing a data structure every interval that briefly highlights when something changed since the last print. [22:51] Can you give me more details of your use case? [22:56] <[Coke]> I often run https://github.com/Raku/Blin/blob/main/util/summarize-overview.raku in a `while [1]; do clear; ./util/summarize-overview.raku` - would be nifty if it remembered the last printed keys/values, and gave a flash of highlight for a few seconds that faded. then I could see number go up more easily [23:06] Oh that does seem useful. How many different status values are there (or equivalently, what's the maximum cardinality of %counts)? [23:11] OIC from your update in #raku-dev, at least the Fail status can have as many copies as there are individual failing modules. Hmmm. [23:18] *** thowe left [23:19] [Coke]: Is https://github.com/Raku/Blin/blob/7e55f9bb88d1352812092e2df5c9b258dcddc2da/bin/blin.p6#L445-L455 the definitive list? [23:22] Ah yes, confirmed at https://github.com/Raku/Blin/blob/7e55f9bb88d1352812092e2df5c9b258dcddc2da/lib/Blin/Processing.rakumod#L50-L56 [23:24] *** thowe joined