🦋 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.
00:00 reportable6 left 00:03 reportable6 joined 01:13 shareable6 left, greppable6 left, benchable6 left, bisectable6 left, bloatable6 left, squashable6 left, nativecallable6 left, unicodable6 left, statisfiable6 left, linkable6 left, evalable6 left, notable6 left, coverable6 left, releasable6 left, reportable6 left, committable6 left, tellable6 left, quotable6 left, sourceable6 left, committable6 joined 01:14 benchable6 joined, shareable6 joined, unicodable6 joined, coverable6 joined, notable6 joined, squashable6 joined 01:15 releasable6 joined, statisfiable6 joined, evalable6 joined, greppable6 joined, reportable6 joined, bisectable6 joined, quotable6 joined, nativecallable6 joined, tellable6 joined, sourceable6 joined 01:16 bloatable6 joined, linkable6 joined 02:39 squashable6 left 02:42 squashable6 joined
japhb leont: github.com/Leont/app-prove6/issues/19 03:31
lizmat: Finally figured out what broke in my backwards-compatibility CI ^^
leont It's not obvious to me why that would break 03:32
japhb There were some Rakudo reliability and thread-safety commits from the time period, starting from one I found that affected $*CWD 03:38
But that was the first Rakudo commit (and first App::Prove6 commit) that could flip things from broken to working or vice-versa. 03:39
leont: ^^
05:06 squashable6 left 05:09 squashable6 joined 06:00 reportable6 left 06:02 reportable6 joined 07:22 squashable6 left 07:23 squashable6 joined 07:38 Voldenet_ joined 07:46 Voldenet left, discord-raku-bot left, Voldenet_ is now known as Voldenet 08:34 Xliff joined 08:53 discord-raku-bot joined 08:54 sena_kun left 08:56 normietotechie[m left 08:58 sena_kun joined
Xliff Raku-GLib suite timing statistics for Raku 2023.02.219.ge.5.e.5.acb.41 09:13
Total number of projects: 33 (503300 loc)
Total non-parallel compile times: 8737.780 (264.781 avg)
Total parallel compile times: 2188.552 (66.320 avg) 3.992x speedup
lizmat slightly better than the last time? 09:14
irclogs.raku.org/search.html?query...nversation 09:15
09:22 normietotechie[m joined 09:35 normietotechie[m left 09:40 normietotechie[m joined 10:15 normietotechie[m left
lizmat Does anybody remember why the separator between leading/trailing declarator pod lines was changed from \n to space? github.com/rakudo/rakudo/commit/e5...e384bd050a 10:33
the commit message isn't really helpful., and that change goes against what S26 has speculated about
but spectests have enshrined that behaviour :-( 10:34
it feels wrong to me, as you use formatting information that way?
although I think there's one reason I can think of: after that change, a newline would indicate the boundary between leading and trailing pod 10:35
when calling .content
OTOH, you wouldn't be able to see difference between leading and trailing if there was only leading or trailing pod 10:36
Geth rakudo/main: ef05ef1e2b | (Elizabeth Mattijsen)++ | src/core.c/Pod.pm6
Introduce Pod::Declarator class

This is basically the Pod::Block::Declarator class, but no longer a subclass of Pod::Block, as Pod declarators are not Pod::Blocks as per S26. This loses two unused attributes per pod declarator.
Created a Pod::Block::Declarator class as a subclass of Pod::Declarator to remain source compatible.
10:51 normietotechie[m joined 12:00 reportable6 left 12:01 reportable6 joined
Xliff limat: Actually... 20% worse. 12:10
Regular timings were down. 12:11
I'm going to have to build a dedicated timing machine at some point, so I don't have system level tasks colliding with it. I'm running this with all cores, so I'm starting to wonder if that's just too much load on the system and its shaking out as chaotic lockling times. 12:12
A dedicated single-user system would answer that question.
[Coke] m: (8737.780).polymod(60, 60, 24).reverse.say 13:20
camelia (0 2 25 37.78)
14:45 ab5tract left 15:18 vrurg_ joined, vrurg left
tonyo [Coke]++ i'm desperate for a tool like that that just works..one of the only things i miss in go is godoc 15:21
[Coke] I think the current user experience is not great: you have to clone the docs, index them with a separate command, and then you can use the installed command line tool. Should be a one stop install with the indexing done and build time. 15:27
lizmat Xliff: re timings, I wonder if the parallel timing could benefit from using 1 CPU less than that you actually have 17:27
18:00 reportable6 left 18:01 reportable6 joined
Geth rakudo/main: 9cc7cfe08b | (Elizabeth Mattijsen)++ | t/12-rakuast/sub.rakutest
RakuAST: add a bare sub, just to be sure
18:41 vrurg_ left
tonyo just uploaded fez v45, now has a bunch of dist management functions 19:03
better usage (and command guessing)
19:04 vrurg joined
Xliff lizmat: That is a thought. 19:06
I might want to drop down to physical cores. 19:07
tonyo .tellable fez v45, full dist management 19:12
hmm, can never remember the right one
.weekly fez v45, full dist management
is there an easy way to view the rendered rakudo docs locally before i submit a PR? 19:26
lucs tonyo: Do you mean rendered from for example a generated README.md? 20:54
tonyo i can't get the docs-website to render twice. i'm trying to add some info to the docs.raku.org about dist management 20:55
lucs Maybe the raku-doc channel people can help. 20:57
Nemokosch what does "render twice" mean? 21:15
tonyo renders the first time (when it does the initial clone) but upon rerunning, it produces the error in the pastebin 21:17
Nemokosch sounds new but I haven't built in a while 21:21
hm, it did work for me but anyway, let's try the "second render" 22:03
hm, seems to work 22:10
only now I realize that it could easily be an upgrade of a dependent module or something, that I already have
22:16 sena_kun left
lol, Doc::TypeGraph:ver<> doesn't even install without test failures 22:35
22:38 squashable6 left 22:40 squashable6 joined
okay, so here it goes, with up-to-date dependencies... 22:42
anyway... it still works 23:11
23:24 squashable6 left 23:27 squashable6 joined