01:03 notable6__ joined, quotable6 left, notable6 left, bisectable6 left, linkable6 left, unicodable6 left, sourceable6__ left, coverable6 left, benchable6 left, releasable6 left, quotable6 joined, bisectable6 joined, linkable6 joined 01:04 nativecallable6_ left 01:05 nativecallable6 joined 01:07 benchable6 joined 01:29 nine left 01:30 nine joined 06:26 Geth left 06:45 quotable6 left, quotable6 joined, bisectable6 left 06:57 timo2 left, timo2 joined
ab5tract timo: if it's still in a branch, let's get it merged after this release is pressed 09:36
Then we can ship it in time for Christmas, hopefully with a few other goodies
11:12 Geth joined
Geth rakudo/main: 483307f7c8 | (Elizabeth Mattijsen)++ | src/core.c/RakuAST/Deparse.rakumod
RakuAST: don't show signature on regex/rule/token

If no actual parameters are specified, which is the most common case
11:14
ab5tract still so confused about CurriedRoleHOWs .. why don't they have a body_block? is the curried_role always a ParametricRoleGroupHOW? why aren't CurriedRoleHOWs designed to do all of the things (body_block, signatured) required to $group.add_possibility? 12:34
why doesn't the body_block live on the role group instead of the (when is it used?) ParametricRoleHOW? 12:39
13:27 ds7823 joined 13:30 ds7823 left 13:39 ds7823 joined 13:41 ds7823 left 13:43 ds7823 joined
ab5tract wonders if maybe Rakudo source should ship with an LLM that can explain it 13:56
14:15 ds7823 left 14:57 guifa joined
timo2 i have a relatively simple program with multiple worker start blocks and the thread pool scheduler keeps adding more and more worker threads because it thinks there may be a deadlock because per-core utilization is too low :| 16:17
meanwhile, usage of the rakudo process goes up above 1k% 16:20
actually i might have done something wrong 16:30
yeah i absolutely did something wrong :) 16:31
lizmat make sure that each batch in the start block does sufficient processing :) 17:58
18:00 [Coke]_ joined 18:03 [Coke] left
timo2 the start blocks are for the lifetime of the program, not for individual tasks 18:42
lizmat why not just do a Thread.run then? 19:01
timo2 yeah i guess i could 19:03
Geth rakudo: dwarring++ created pull request #5980:
Fix DEPARSE on unamed (anonymous) packages.
19:18
rakudo/main: 0b5bb196d6 | (Elizabeth Mattijsen)++ | src/core.c/RakuAST/Deparse.rakumod
RakuAST: fix deparsing of nameless package-like constructs

As spotted by David Warring++ Fixed #5979
19:28 guifa left 19:32 guifa joined, ab5tract_ joined 19:33 [Coke]_ is now known as [Coke]
[Coke] releasable6 died? 19:34
lizmat looks like all bots are down again [Coke] will you do the honours? 19:35
19:35 sivoais_ joined 19:36 ab5tract left, camelia left, ab5tract_ is now known as ab5tract, ugexe left 19:37 sivoais left
[Coke] on it 19:37
19:38 linkable6 left, greppable6__ left, committable6 left, benchable6 left, nativecallable6 left, notable6__ left, quotable6 left, bloatable6 left, evalable6 left 19:40 shareable6 joined, linkable6 joined, releasable6 joined, bloatable6 joined 19:41 committable6 joined, greppable6 joined, tellable6 joined, evalable6 joined, bisectable6 joined 19:42 coverable6 joined, sourceable6 joined 19:43 unicodable6 joined, benchable6 joined, nativecallable6 joined, notable6 joined, quotable6 joined 19:47 ugexe joined, jdv joined
jdv lizmat: what's the usual dance you do to rename stuff in git? 19:48
lizmat git mv
jdv i thought i've seen multiple commit setups
lizmat or if it's many file:
rak --rename-file '*.subst(".t",".rakutest")' t 19:49
to rename all files in the t directory to their new raku extensions
--rename-files
jdv there's something where you've done a double move but i can't find it 19:50
lizmat ?? what you mean with a double move?
19:51 camelia joined
jdv i just remember something odd from a few times doing the changelogs and i became curious cause i'm about ot move a bunch of stuff in a rando personal repo 19:52
lizmat sorry, I haz no idea 19:55
rak will rename with `git mv' if it sees the file is under git control 19:56
otherwise it will just do a rename
20:00 camelia left
jdv i guess i was just remembering stuff like this: git log --stat e42457^..75370b 20:01
no idea why. happy thursday. 20:02
[Coke] releasable6: next 20:07
releasable6 [Coke], Next release in ≈1 day and ≈22 hours. There are no known blockers. 14 out of 19 commits logged
[Coke], Details: gist.github.com/def14ee736f6174bb6...867cce8b82
[Coke] releasable6: next 20:08
releasable6 [Coke], Next release in ≈1 day and ≈22 hours. There are no known blockers. 19 out of 19 commits logged
20:23 camelia joined 20:39 melezhik_ joined 20:47 melezhik_ left, melezhik_ joined 21:18 melezhik_ left 22:10 ds7823 joined 22:38 Geth left 22:49 ds7823 left 23:16 librasteve_ left