[00:46] *** [Coke] left
[02:42] *** [Coke] joined
[02:45] <[Coke]> doing the redo run now. most have a few dozen modules to test, this one up to 420

[02:46] <[Coke]> so many locked copies of rakudo

[03:13] <Geth> ¦ rakudo: ugexe++ created pull request #6687: RakuAST: fix thunks stacked over a WhateverCode

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

[05:03] <Geth> ¦ rakudo/main: ee62d82647 | (Nick Logan)++ | 3 files

[05:03] <Geth> ¦ rakudo/main: RakuAST: declare code in a WhateverCode only in the WhateverCode

[05:03] <Geth> ¦ rakudo/main: 

[05:03] <Geth> ¦ rakudo/main: Previously a thunk declared the code and variables of its expression in

[05:03] <Geth> ¦ rakudo/main: its own block even when an inner thunk evaluated the expression. A

[05:03] <Geth> ¦ rakudo/main: WhateverCode is such an inner thunk, and a constant's value, a

[05:03] <Geth> ¦ rakudo/main: parameter default and a loop statement modifier all wrap one more

[05:03] <Geth> ¦ rakudo/main: thunk around it. A block, pointy block, regex, signature literal or

[05:03] <Geth> ¦ rakudo/main: <…commit message has 9 more lines…>

[05:03] <Geth> ¦ rakudo/main: review: https://github.com/rakudo/rakudo/commit/ee62d82647

[05:03] <Geth> ¦ rakudo/main: 11177343c6 | (Nick Logan)++ | 2 files

[05:03] <Geth> ¦ rakudo/main: RakuAST: allow a condition modifier over a WhateverCode in a loop

[05:03] <Geth> ¦ rakudo/main: 

[05:03] <Geth> ¦ rakudo/main: Previously a statement with both a condition and a loop modifier died

[05:03] <Geth> ¦ rakudo/main: with "Condition modifier thunk cannot wrap an inner thunk" at compile

[05:03] <Geth> ¦ rakudo/main: time when its expression was a WhateverCode, as in

[05:03] <Geth> ¦ rakudo/main: `(*.succ if 1 for 1)`. The condition modifier thunk expected to be the

[05:03] <Geth> ¦ rakudo/main: innermost thunk, but the WhateverCode's thunk was already there.

[05:03] <Geth> ¦ rakudo/main: 

[05:03] <Geth> ¦ rakudo/main: This has the condition modifier thunk declare the inner thunk and wrap

[05:03] <Geth> ¦ rakudo/main: its value.

[05:03] <Geth> ¦ rakudo/main: review: https://github.com/rakudo/rakudo/commit/11177343c6

[05:03] <Geth> ¦ rakudo/main: 98a6ae6b7b | (Nick Logan)++ (committed using GitHub Web editor) | 3 files

[05:03] <Geth> ¦ rakudo/main: Merge pull request #6687 from ugexe/ugexe/rakuast-stacked-thunk-decls

[05:03] <Geth> ¦ rakudo/main: 

[05:03] <Geth> ¦ rakudo/main: RakuAST: fix thunks stacked over a WhateverCode

[05:03] <Geth> ¦ rakudo/main: review: https://github.com/rakudo/rakudo/commit/98a6ae6b7b

[06:52] *** gfldex left
[07:19] *** gfldex joined
[08:22] <lizmat> re startup timing: I think I found the reason why I'm seeing 0.06 and 0.08 startup times

[08:22] <lizmat> it appears that the processor in my MBP (M4 Max) has slow (efficient) and fast cores

[08:25] <lizmat> I noticed that if I'm running a single core process in one window, the bare startup is .06, if there are no other (long) running processes, the startup is .08

[08:25] <lizmat> so if it's busy, it's using a fast core, otherwise it's using an efficient core

[09:14] <Geth> ¦ rakudo/main: ff41340331 | (Elizabeth Mattijsen)++ | src/Raku/ast/base.rakumod

[09:14] <Geth> ¦ rakudo/main: RakuAST: make sure Node.apply-sink accepts :$okifnil

[09:14] <Geth> ¦ rakudo/main: 

[09:14] <Geth> ¦ rakudo/main: Expression.apply-sink has this named argument, that is apparently

[09:14] <Geth> ¦ rakudo/main: being used in some situation.  But in some situations, Node.apply-sink

[09:14] <Geth> ¦ rakudo/main: is being called with it and then fails.

[09:14] <Geth> ¦ rakudo/main: 

[09:14] <Geth> ¦ rakudo/main: This unbreaks the RakuAST::Utils module.

[09:14] <Geth> ¦ rakudo/main: review: https://github.com/rakudo/rakudo/commit/ff41340331